Has happened to me also, I think it's to do with the rails_rcov plugin and it adding custom rake tasks for rcov.
As i've been in control of the servers, I just installed the rcov gem, but you might not be able to do that. Best, Dave On 6 May 2007, at 19:18, Jamis Buck wrote: > > I've seen this before, and I haven't yet figured out what is going > on. The "problem" is that for some reason, "rake db:migrate" is > running the unit tests, and "cap migrate" calls "rake db:migrate". It > is almost certainly something environmental, on the machine where the > migrations are being run, and it hasn't happened to me in some time. > If anyone knows what is up with this, please do speak up. > > - Jamis > > On May 6, 2007, at 11:43 AM, Marcus Ahnve wrote: > >> >> Hi, >> >> I'm using RSpec and Capistrano, and 'cap migrate' fails in >> production, >> since RSpec is only loaded in development. >> >> Does anyone know why RSpec is loaded when 'cap migrate' is run? >> >> Cheers /Marcus >> >> -- >> http://marcus.ahnve.net >> >>> > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
