-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
recycled object error #42
Comments
I'm getting this same error on Ruby 1.9.3, Rails 3.2.3, spork (1.0.0rc3), spork-testunit (0.0.8). Both spork libs via git. Has anyone figured out a solution for this?
I notice that drb is running out of RVM_PATH/lib/ruby/1.9.1 but I am using ruby 1.9.3. Maybe that is part of the issue? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am using MRI 1.9.3, Rails 3.2.1, spork 0.9.0, test-unit 2.4.5, and spork-testunit. Regardless of whether I use spork-testunit 0.0.7 or the latest git master, I get this 'recycled object' error from
bundle exec testdrb
:I experimented with trimming the list of tests run, and found that it is triggered by any test which has an error (not a failure). When triggered, one of two things happen: (1) the above stack trace, or (2) what should be the summary line in the output (e.g. something like
20 tests, 106 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
) actually ends up being complete garbage, e.g.So it looks to me like some memory pointer has gone AWOL and this string just gets plucked from a random memory area. Ouch!
Given that it is the summary line which goes FUBAR, I strongly suspect that this is related to issue #33. However, this happens even after I manually edited
testdrb
to prevent it getting confused by the presence of theminitest
gem.This is the final straw for me. I've had endless woes trying to get Spork and Guard to play nice with both test-unit and minitest, so I'm going to switch to RSpec which is hopefully a more well-trodden and reliable path.
The text was updated successfully, but these errors were encountered: