Since rails r9244 edge rspec_on_rails specs fail
Reported by Ian White | April 11th, 2008 @ 01:57 PM | in No-Milestone-Assigned
Since rails r9244, the pre_commit_rails suite fails edge with:
SQLite3::SQLException: no such table: schema_migrations: SELECT version FROM schema_migrations
(full trace below)
The reason seems to be that in r9244 the table name for schema info changed to schema_migrations (see http://dev.rubyonrails.org/ticke... for the ticket that produced the change).
Full trace:
rake aborted!
SQLite3::SQLException: no such table: schema_migrations: SELECT version FROM schema_migrations
/Users/ian/Development/git/rspec-dev/example_rails_app/vendor/rails/edge/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:151:in `log'
/Users/ian/Development/git/rspec-dev/example_rails_app/vendor/rails/edge/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:132:in `execute'
/Users/ian/Development/git/rspec-dev/example_rails_app/vendor/rails/edge/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:353:in `catch_schema_changes'
/Users/ian/Development/git/rspec-dev/example_rails_app/vendor/rails/edge/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:132:in `execute'
/Users/ian/Development/git/rspec-dev/example_rails_app/vendor/rails/edge/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:150:in `select_rows'
/Users/ian/Development/git/rspec-dev/example_rails_app/vendor/rails/edge/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:27:in `select_values'
/Users/ian/Development/git/rspec-dev/example_rails_app/vendor/rails/edge/activerecord/lib/active_record/migration.rb:367:in `current_version'
/Users/ian/Development/git/rspec-dev/example_rails_app/vendor/rails/edge/activerecord/lib/active_record/migration.rb:335:in `migrate'
/Users/ian/Development/git/rspec-dev/example_rails_app/vendor/rails/edge/railties/lib/tasks/databases.rake:99
/opt/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:546:in `call'
/opt/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:546:in `execute'
/opt/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:541:in `each'
/opt/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:541:in `execute'
/opt/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:508:in `invoke_with_call_chain'
/opt/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:501:in `synchronize'
/opt/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:501:in `invoke_with_call_chain'
/opt/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:494:in `invoke'
/opt/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1931:in `invoke_task'
/opt/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1909:in `top_level'
/opt/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1909:in `each'
/opt/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1909:in `top_level'
/opt/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1948:in `standard_exception_handling'
/opt/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1903:in `top_level'
/opt/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1881:in `run'
/opt/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1948:in `standard_exception_handling'
/opt/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1878:in `run'
/opt/local/lib/ruby/gems/1.8/gems/rake-0.8.1/bin/rake:31
/opt/local/bin/rake:16:in `load'
/opt/local/bin/rake:16
(in /Users/ian/Development/git/rspec-dev/example_rails_app)
Comments and changes to this ticket
-
David Chelimsky April 14th, 2008 @ 01:06 PM
- → Milestone changed from “No-Milestone-Assigned” to “1.1.4”
- → State changed from “new” to “open”
- → Assigned user changed from “” to “David Chelimsky”
-
Ian White April 14th, 2008 @ 06:47 PM
I've determined that this is a rails bug -- I can reproduce this on a fresh rails app, with no rspec particulars. I'm report the rails ticket here when I've investigated further, and reported the problem.
-
-
Ian White April 15th, 2008 @ 12:37 PM
(Add your +1s to the above rails ticket, if you feel so inclined)
-
Ian White April 17th, 2008 @ 08:53 PM
This is now fixed in rails (http://github.com/rails/rails/co...)
(I guess the next thing is cloning rails from git, instead of subversion in the example_rails_app)
-
David Chelimsky April 17th, 2008 @ 08:59 PM
- → State changed from “open” to “resolved”
Cool - closing this. Thanks for staying up on it Ian.
-
David Chelimsky April 17th, 2008 @ 09:00 PM
- → Milestone changed from “1.1.4” to “No-Milestone-Assigned”
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Behaviour Driven Development for Ruby.
