Hello everyone I'm running my rake task in the application on the command line, and the tests are running ok. RAILS_ENV=test rake glam:build desc "Prepare for CI and run entire test suite" task :build => ['db:migrate', 'features'] do end When I use the UI I initially point to a bash script to copy the database file over and run the gem bundle #!/bin/sh cp /var/www/rails/database.yml config/ /usr/bin/gem bundle and then run the rake task, so the build command looks like this /path/to/bash_script && RAILS_ENV=test rake glam:build I'm having errors appear using this method, the most recent one is this can't activate rack (~> 1.0.0, runtime) for [], already activated rack-1.1.0 for [] (RuntimeError) I've been reading this blog post, and the app I'm testing is using bundler as well. http://groups.google.com/group/integrityapp/browse_thread/thread/1755f822551617ac I've just upgraded to v0.2.3 of integrity and was wondering if this patch was built in or not? Or how do I go about patching v0.2.3 if needed?
On Jan 12, 2010, at 6:16 AM, Matt Davies wrote: > can't activate rack (~> 1.0.0, runtime) for [], already activated > rack-1.1.0 for [] (RuntimeError) > You can try updating the Gemfile in integrity's root directory gem "rack", "1.0.0" to gem "rack", "1.1.0" TJ
Hi TJ, Rack isn't described in the gemfile, it'll be a dependency of some other gem no doubt, and it's coming down as 1.1.0, thats not the problem. I think rack 1.1.0 has some issues 2010/1/12 TJ Singleton <tj@deepsalt.com>: > > On Jan 12, 2010, at 6:16 AM, Matt Davies wrote: > >> can't activate rack (~> 1.0.0, runtime) for [], already activated >> rack-1.1.0 for [] (RuntimeError) >> > > > You can try updating the Gemfile in integrity's root directory > gem "rack", "1.0.0" to gem "rack", "1.1.0" > > TJ >