Skip to content
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

Open
victornamuso opened this issue Nov 8, 2011 · 10 comments
Open

#<DRb::DRbUnknown:0x007fdfb22d2898> instead of summary #33

victornamuso opened this issue Nov 8, 2011 · 10 comments

Comments

@victornamuso
Copy link

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.

@nixme
Copy link
Member

nixme commented Nov 8, 2011

Hmm... are you by chance using Test::Unit on MRI 1.9.2?

@victornamuso
Copy link
Author

Yes

@nixme
Copy link
Member

nixme commented Nov 13, 2011

Hrm... I'm wondering whether it's better to split up this gem into spork-minitest and spork-testunit since they both have completely different code paths at this point. We'd also stop breaking people when changes are made like this.

Anyone have a better idea?

@abelmartin
Copy link

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?

@aspiers
Copy link

aspiers commented Jan 8, 2012

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 :-(

@aspiers
Copy link

aspiers commented Jan 13, 2012

@nixme: yes, sounds like a good idea to split off spork-minitest into a separate gem.

@aspiers
Copy link

aspiers commented Jan 29, 2012

I looked into this further. The problem is at the top of testdrb where it first tries to require 'minitest/unit', and then reverts to test/unit on LoadError. This is not a valid approach, because the presence of minitest does not guarantee that you are using it. I am on MRI 1.9.3 + Rails 3.2.1, and minitest is installed because several gems including rake and rdoc depend on it - so in fact minitest is pretty much guaranteed to be installed in any modern Rails environment! However, I am using the guard-test gem to launch Spork, so my DRb server is set up to run with test/unit not minitest. (This was a deliberate choice because last time I looked, guard-minitest was riddled with issues.)

So I strongly recommend that the minitest support should be syphoned off into spork-minitest to avoid further calamity.

@gabeodess
Copy link

I too would like this fixed!

@djmaze
Copy link

djmaze commented Jul 8, 2012

Removed minitest support in my own fork. You might like to use it in the meantime: https://github.com/djmaze/spork-testunit

@martinos
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants