Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Cukes failing on JRuby 1.6.0 #344

Closed
kaiwren opened this Issue Mar 27, 2011 · 1 comment

Comments

Projects
None yet
2 participants
Contributor

kaiwren commented Mar 27, 2011

I've been looking into this and I suspect @myronmarston has run into this already with aslakhellesoy/aruba#27

The problem seems to lie in the assumption that Cucumber in general and Aruba in particular will run on all Ruby runtimes that RSpec supports.

Perhaps we should re-work the cukes to use a 'safe' runtime while allowing us to run rspec itself using a configurable interpreter. Something like
rake cucumber RSPEC_RUNTIME=/Users/sidu/.rvm/rubies/jruby-head/bin/ruby

Contributor

kaiwren commented Jun 25, 2011

A great deal has improved since the last time I looked at this - there's no problem running the cuke build on Jruby anymore (except that its horribly slow because of all the JVMs being created, so any CI server will have its CPU pegged).

All that needs to be done is to increase the aruba timeout to about 60s when on jruby and fix a couple of scenarios that are breaking because of the difference in backtraces from CRuby to JRuby. I should have a pull request in for this tomorrow.

@kaiwren kaiwren added a commit to c42engineering/rspec-core that referenced this issue Jul 10, 2011

@kaiwren kaiwren Issue #344 - Increase Aruba's timeout to compensate for JVM startup 74b9391

@dchelimsky dchelimsky closed this in e2cfa43 Oct 9, 2011

@dchelimsky dchelimsky added a commit that referenced this issue Oct 9, 2011

@dchelimsky dchelimsky ci: add jruby to travis config
- #344.
cf80330
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment