-
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
#<DRb::DRbUnknown:0x007fdfb22d2898> instead of summary #33
Comments
Hmm... are you by chance using Test::Unit on MRI 1.9.2? |
Yes |
Hrm... I'm wondering whether it's better to split up this gem into Anyone have a better idea? |
I just came across this. I'm using MRI 1.8.7, Rails 3.0.10, Test::Unit. Is there another gem that I should be using for Test::Unit to interpret the object? |
I have the same problem with 0.0.7, MRI 1.9.3, and Rails 3.1.3. Downgrading to 0.0.6 fixes it :-( |
@nixme: yes, sounds like a good idea to split off |
I looked into this further. The problem is at the top of So I strongly recommend that the minitest support should be syphoned off into |
I too would like this fixed! |
Removed minitest support in my own fork. You might like to use it in the meantime: https://github.com/djmaze/spork-testunit |
Thanks @djmaze, you version works well with my functional and unit test. However my integration tests are running but I can't see my tests outputs. I will investigate on it. |
Upon moving to 0.0.7 from 0.0.6, I now get #DRb::DRbUnknown:0x007fdfb22d2898 instead of the summary line (x tests, x assertions, x failures, etc...). Solely rolling back to 0.0.6 in my gemfile fixes the issue. The tests appear to be running because I do get visual feedback of the failure/error if one occurs.
The text was updated successfully, but these errors were encountered: