BigTuna is not missing constant VCS about bigtuna

[michalbugno]

Please provide some more info:
Which version/commit are you using? What is your environment/system? What where your installation steps? Any "non-standard" things we might want to know about?

We'd like to reproduce this bug (it appears to be rails-related)

[brupm]

I have deployed https://github.com/appelier/bigtuna/commits/0.1.1 to Engine Yard's appcloud which is basically ec2.

When I run the same steps manually while ssh'd on the server they all work. I am running the app and all commands under the same user deploy, group deploy so it is not a permission's issue.

No non-standard things.

Installation steps for bigtuna were, clone the app, deploy to server with chef, really a standard basic deploy. Big tuna runs, clones the repos under it's own builds folder but it seems to not execute the steps.

[michalbugno]

My guess is that this is a rails magic class loader issue. I cannot reproduce it, but try this branch:

https://github.com/appelier/bigtuna/tree/missing_constant_fix

It loads the bigtuna-related classes manually in the rails app initializer instead of relying on rails loader. Hope this helps.

[thibaudgg]

I got exactly the same problem (git 1.7.2.2 /mac os x server 10.6).
Build is green with no output and delayed_job log tell ArgumentError: BigTuna is not missing constant VCS! - 0 failed attempts
Using missing_constant_fix branch do not solve this issue.

Any others ideas?

[michalbugno]

I can't reproduce the bug. What version of ruby and ruby on rails are you running? What is delayed job's version? (I know bundler should take care of those, but you never know...)

Are you able to share the code you are running with bigtuna? Maybe the code which is executes is in conflict with bigtuna's code (regarding rails/bundler)

[thibaudgg]

We use ruby-1.8.7-p330 (via RVM) and our Gemfile.lock: https://gist.github.com/766048
(seems to be the same as yours)

Sadly I'm not able to share the code we're running with bigtuna. It's a quite complicated Rails 3.0.3 app on ruby 1.9.2 with a lot of gem dependencies. But I think this issue appear even before the steps can be run.

Thanks for your help!

[brupm]

It does seem to be happening before the steps can run. I am running rails 2.3.10 and ruby 1.8.7. Same here can't really share the code.

these are the gems I am using
https://gist.github.com/766429

[michalbugno]

Guys, could you try the missing_constant_fix branch once again?

https://github.com/appelier/bigtuna/tree/missing_constant_fix

I removed the require_dependency and replaced it with require in the initializer. I am still unable to reproduce the bug, but my best shot is that the "is not missing" is connected with rails's require dependency.

[thibaudgg]

Are you sure to have pushed to the missing_constant_fix? The last commit has 5 days old. Thx.

[michalbugno]

Crap ;-)

[brupm]

/data/BigTuna/current/log $ tail delayed_job.log
2011-01-08T07:33:43-0800: [Worker(delayed_job host:ip-10-102-75-206 pid:20674)] Exiting...
2011-01-08T07:33:47-0800: [Worker(delayed_job host:ip-10-102-75-206 pid:7123)] Starting job worker
2011-01-08T07:35:18-0800: [Worker(delayed_job host:ip-10-102-75-206 pid:7123)] Build #1 @ January 08, 2011 15:35 failed with ArgumentError: BigTuna is not missing constant VCS! - 0 failed attempts
2011-01-08T07:35:18-0800: [Worker(delayed_job host:ip-10-102-75-206 pid:7123)] PERMANENTLY removing Build #1 @ January 08, 2011 15:35 because of 1 consecutive failures.
2011-01-08T07:35:18-0800: [Worker(delayed_job host:ip-10-102-75-206 pid:7123)] 1 jobs processed at 0.1745 j/s, 1 failed ...
2011-01-08T07:36:10-0800: [Worker(delayed_job host:ip-10-102-75-206 pid:7123)] Build #2 @ January 08, 2011 15:36 failed with ArgumentError: BigTuna is not missing constant VCS! - 0 failed attempts
2011-01-08T07:36:10-0800: [Worker(delayed_job host:ip-10-102-75-206 pid:7123)] PERMANENTLY removing Build #2 @ January 08, 2011 15:36 because of 1 consecutive failures.
2011-01-08T07:36:10-0800: [Worker(delayed_job host:ip-10-102-75-206 pid:7123)] 1 jobs processed at 0.3579 j/s, 1 failed ...

It's so weird, there is not much in the log. I did deploy the latest code.

[michalbugno]

Sorry guys, but we just can't reproduce it. If you are willing to help, you may try to fix it on your own and we will gladly accept your fixes. If you do, my suggestion is to modify the delayed_job code responsible for the "failed with " message and get the backtrace from the exception which is available there. Backtrace might tell us something.

https://github.com/collectiveidea/delayed_job/blob/master/lib/delayed/worker.rb

Line 168 fails.

If you don't want to modify the code you may want to change the bigtuna's default job reschedules to more than 1 and see the database entry in delayed job's table for the recent error (job.last_error on line 167)

[michalbugno]

https://github.com/appelier/bigtuna/issues/closed#issue/33
Closing.