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

Test suite fails with Ruby 2.0 #50

Closed
voxik opened this issue Feb 20, 2013 · 4 comments
Closed

Test suite fails with Ruby 2.0 #50

voxik opened this issue Feb 20, 2013 · 4 comments

Comments

@voxik
Copy link
Contributor

voxik commented Feb 20, 2013

Running the test suite against Ruby 2.0, I observe following error:

$ rspec spec
.............*...............F..

Pending:
  ChildProcess lets a detached child live on
    # how do we spec this?
    # ./spec/childprocess_spec.rb:132

Failures:

  1) ChildProcess::Unix::Process behaves like a platform that provides the child's pid knows the child's pid
     Failure/Error: process.pid.should == file.read.chomp.to_i
       expected: 21313
            got: 21310 (using ==)
     Shared Example Group: "a platform that provides the child's pid" called from ./spec/unix_spec.rb:7
     # /usr/share/ruby/tempfile.rb:324:in `open'

Finished in 2.77 seconds
32 examples, 1 failure, 1 pending

Failed examples:

rspec ./spec/pid_behavior.rb:4 # ChildProcess::Unix::Process behaves like a platform that provides the child's pid knows the child's pid

These are gems installed on my system:

$ gem list

*** LOCAL GEMS ***

bigdecimal (1.1.0)
diff-lcs (1.1.3)
io-console (0.4.1)
json (1.7.7)
psych (2.0.0)
rake (10.0.3)
rdoc (4.0.0.rc.2.1)
rspec (2.12.0)
rspec-core (2.12.2)
rspec-expectations (2.12.1)
rspec-mocks (2.12.2)
@jarib
Copy link
Collaborator

jarib commented Feb 20, 2013

Can you provide some more info about your system/OS and the exact Ruby version you're running? The latest release passes using ruby-head on Travis.

@voxik
Copy link
Contributor Author

voxik commented Feb 20, 2013

I found the issue. It is script similar to rbenv executing ruby as a new process. Using 'exec' solves my issues.

@voxik voxik closed this as completed Feb 20, 2013
@voxik
Copy link
Contributor Author

voxik commented Feb 20, 2013

Sorry for the noise and thank you.

@jarib
Copy link
Collaborator

jarib commented Feb 20, 2013

No worries.

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

2 participants