This project is archived and is in readonly mode.
"loud" migrations + test db prep
Reported by Matt Jankowski | July 21st, 2008 @ 05:20 PM | in 2.1.1
We're seeing issues in current 2.1 stable where the test database is not correctly prepared, and a manual db:migrate on the test env is required to get tests passing. It looks like one commit to master was brought over to 2.1, but a second one may have been forgotten?
Commits to master...
http://github.com/rails/rails/co...
http://github.com/rails/rails/co...
Commits to 2.1...
Comments and changes to this ticket
-
Jeremy Kemper August 20th, 2008 @ 05:17 PM
- Milestone changed from 2.x to 2.1.1
- State changed from new to resolved
Cherry-picked it. Thanks Matt!
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Attachments
Tags
Referenced by
- 757 rake test wipes out the entire development db This actually looks like a duplicate of #670
- 757 rake test wipes out the entire development db http://rails.lighthouseapp.com/p...
- 757 rake test wipes out the entire development db Closing as duplicate of #670