Rails: Problem with test-environment and mysql2 database

Ruby
#1

Hi list,
this is the first time I am posting here, so please be gentle :wink:

I have spent all day yesterday googeling and reading stuff, and the
only post I found having the same problem as I did was replied to
by the owner with “fixed it, was something in my database.yml”, what
didn’t help me the slightest bit, so please help me, ruby-wan, you are
my last hope.

I have a Rails-project (OS X Snow Leopard, Rails 3.0.3, all gems are up
to date, although we got the test reproduced on another unix) that I am
supposed to test. It’s pretty simple, a basic implementation of an
access control system using the devise gem.

My problem here is that I can’t run any tests. The test I try to run
is the auto-generated test for my autogenerated dummy-controller that
doesn’t do anything, and that doesn’t work for, stacktrace:

/Library/Ruby/Gems/1.8/gems/activerecord-3.0.3/lib/active_record/connection_adapters/abstract/connection_specification.rb:62:in
establish_connection': test database is not configured (ActiveRecord::AdapterNotSpecified) from /Library/Ruby/Gems/1.8/gems/activerecord-3.0.3/lib/active_record/connection_adapters/abstract/connection_specification.rb:55:inestablish_connection’
from
/Library/Ruby/Gems/1.8/gems/activerecord-3.0.3/lib/active_record/railtie.rb:59
from
/Library/Ruby/Gems/1.8/gems/activesupport-3.0.3/lib/active_support/lazy_load_hooks.rb:36:in
instance_eval' from /Library/Ruby/Gems/1.8/gems/activesupport-3.0.3/lib/active_support/lazy_load_hooks.rb:36:inexecute_hook’
from
/Library/Ruby/Gems/1.8/gems/activesupport-3.0.3/lib/active_support/lazy_load_hooks.rb:26:in
on_load' from /Library/Ruby/Gems/1.8/gems/activerecord-3.0.3/lib/active_record/railtie.rb:57 from /Library/Ruby/Gems/1.8/gems/railties-3.0.3/lib/rails/initializable.rb:25:ininstance_exec’
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.3/lib/rails/initializable.rb:25:in
run' from /Library/Ruby/Gems/1.8/gems/railties-3.0.3/lib/rails/initializable.rb:50:inrun_initializers’
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.3/lib/rails/initializable.rb:49:in
each' from /Library/Ruby/Gems/1.8/gems/railties-3.0.3/lib/rails/initializable.rb:49:inrun_initializers’
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.3/lib/rails/application.rb:134:in
initialize!' from /Library/Ruby/Gems/1.8/gems/railties-3.0.3/lib/rails/application.rb:77:insend’
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.3/lib/rails/application.rb:77:in
method_missing' from /Users/vivec/Documents/RubyWorkspace/psmt/config/environment.rb:5 from /Users/vivec/Documents/RubyWorkspace/psmt/test/unit/../test_helper.rb:2:inrequire’
from
/Users/vivec/Documents/RubyWorkspace/psmt/test/unit/…/test_helper.rb:2
from
/Users/vivec/Documents/RubyWorkspace/psmt/test/unit/dummy_test.rb:1:in
`require’
from
/Users/vivec/Documents/RubyWorkspace/psmt/test/unit/dummy_test.rb:1

Okay, so my test database isn’t configured, so let’s configure it? Not
that simple, for I simply can’t.

Here’s the database.yml:

development:
adapter: mysql2
encoding: utf8
reconnect: false
database: psmt_dev
pool: 5
username: root
password:
socket: /var/run/mysqld/mysqld.sock

test:
adapter: mysql2
encoding: utf8
reconnect: false
database: psmt_test
pool: 5
username: root
password:
socket: /var/run/mysqld/mysqld.sock

When I try to do anything rakely in development mode, everything is
fine. MySql is up and running, the databases both exist. I can do
a rake db:migrate to the database psmt_dev and, if I change the db
in development mode to psmt_test, I can migrate to that too. (I
did that and hoped it would solve the problem, it did not.)
As soon as I try to do anything rakely in test mode, it crashes -
there seems to be a problem dumping the database:

$ rake db:test:prepare --trace
(in /Users/vivec/Documents/RubyWorkspace/psmt)
** Invoke db:test:prepare (first_time)
** Invoke db:abort_if_pending_migrations (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:abort_if_pending_migrations
** Execute db:test:prepare
** Invoke db:test:load (first_time)
** Invoke db:test:purge (first_time)
** Invoke environment
** Execute db:test:purge
rake aborted!
You have a nil object when you didn’t expect it!
You might have expected an instance of Array.
The error occurred while evaluating nil.[]
/Library/Ruby/Gems/1.8/gems/activerecord-3.0.3/lib/active_record/railties/databases.rake:429
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in call' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:inexecute’
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in each' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:inexecute’
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in
invoke_with_call_chain' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/monitor.rb:242:insynchronize’
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in
invoke_with_call_chain' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:607:ininvoke_prerequisites’
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:604:in each' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:604:ininvoke_prerequisites’
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:596:in
invoke_with_call_chain' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/monitor.rb:242:insynchronize’
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in
invoke_with_call_chain' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:ininvoke’
/Library/Ruby/Gems/1.8/gems/activerecord-3.0.3/lib/active_record/railties/databases.rake:460
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in call' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:inexecute’
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in each' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:inexecute’
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in
invoke_with_call_chain' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/monitor.rb:242:insynchronize’
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in
invoke_with_call_chain' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:ininvoke’
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in invoke_task' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:intop_level’
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in each' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:intop_level’
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
standard_exception_handling' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:intop_level’
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in run' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:instandard_exception_handling’
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in run' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/bin/rake:31 /usr/bin/rake:19:inload’
/usr/bin/rake:19

I chased the bug deep down to databases.rake:429, and there it says:
task :purge => :environment do
abcs = ActiveRecord::Base.configurations
case abcs[“test”][“adapter”]
when /mysql/

and the problem seems to be with the case-statement, there something
is a nil value (and most likely it is the “adapter” value in “test”?).
The adapter value is set in my database.yml, and everything is great
as long as I stay to the development environment - but I need to
get those tests working.

In my theory, the problem is that, to execute a test, Rails wants to
have the test environment running and therefore the test-database dumped
and re-filled from the fixtures. The explosions happen during the dump-
procedure, so I guess, it’s not my fault.

Does anyone have any idea how I get this fixed? I’m helpless.

greetings

#2

Sorry, but you’re on the wrong mailing list. This one is for Ruby (the
programming language), not Rails (the web framework, which happens to be
written in ruby).

There are links from the Rails website pointing to their mailing lists.

#3

vivec manavortex wrote in post #977603:
…

I chased the bug deep down to databases.rake:429, and there it says:
task :purge => :environment do
abcs = ActiveRecord::Base.configurations
case abcs[“test”][“adapter”]
when /mysql/

and the problem seems to be with the case-statement, there something
is a nil value (and most likely it is the “adapter” value in “test”?).
The adapter value is set in my database.yml, and everything is great
as long as I stay to the development environment - but I need to
get those tests working.

Could it be that in the “test” section of database.yml you have a TAB
(instead of 2 spaces)? Maybe that is not the yaml you expect.

Maybe try:

$ cd config
$ irb

require ‘yaml’
=> true
File.open(‘database.yml’) do |f|
YAML::load(f.read)
end
=> {“development”=>{“adapter”=>“sqlite3”,
“database”=>“db/development.sqlite3”, “pool”=>5, “timeout”=>5000},
“test”=>{“adapter”=>“sqlite3”, “database”=>“db/test.sqlite3”, “pool”=>5,
“timeout”=>5000}, “production”=>{“adapter”=>“sqlite3”,
“database”=>“db/production.sqlite3”, “pool”=>5, “timeout”=>5000}}

and see if this is the correct result you expected.

#4

Thanks a lot! That helped me to nail down the problem -
the test-environment-specifications weren’t parsed at all.
After removing the socket specification it now works.

Wow, that was great support, now I wonder what may happen when
I mail to the right mailing list? :wink:

greetings