-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
JRuby 9.1.0.0 error running bundle exec cucumber on Travis #3867
Comments
Travis raw log:
|
Can you reproduce this outside of travis? Does it reproduce if you just run My first guess would be that it's getting versions mixed up somehow and picking a gem home that doesn't have the bundler bits. Could be a RubyGems regression too. |
@headius no, it works locally. I see the bundler version, 1.12.3, is identical across a 9.0.5.0 run and a 9.1.0.0 run. Amateur question - what is next best step to troubleshoot? |
@Capncavedan If you contact Travis support they will point you toward a docker image you can set up to test the same environment locally. If you can reproduce there it should be easier for both of us to investigate the issue. |
It would be worth downgrading RubyGems too. I am starting to suspect something's not right in there. |
FWIW, I was still able to reproduce the very similar #3888 with RubyGems 2.4.8, so I'm less suspicious of RG now. |
I was able to reproduce this with RubyGems 2.5.2, and got a different error with 2.4.x |
Ok, we'll assume it's not RG for now. Still no good leads though. Is there any way we can reproduce this ourselves? This is the big outstanding item holding up 9.1.1.0. |
I haven't been able to reproduce outside of Travis. I earlier had success by instructing Travis to run "rspec" and "cucumber" explicitly, rather than simply "bundle exec rake" Then, after following the explicit steps outlined in the cucumber-rails project to update rails bins and binstubs, this is all working OK now.
This app started out life on Rails 3 and was updated last Fall to Rails 4. I see we also updated to cucumber-rails 1.4.3 (from 1.4.2) in January. So there were quite a few moving parts, one of which apparently finally went haywire with JRuby 9.1.0.0. Thanks for your advice through this, @headius |
Thank you for the follow-up, @Capncavedan. It's certainly possible something got more strict in 9.1, and it's still possible we broke something, but we'll consider your case closed for now. |
Have an issue where 9.1.0.0 throws an error after running rpecs successfully, when it tries to run the cucumbers. 9.0.5.0 with the same gems does not throw the errors.
The error is:
Gem::Exception: can't find executable bundle
Environment
JRuby 9.1.0.0
Travis: Ubuntu 12.04.5 LTS / 3.13.0-29-generic
Expected Behavior
Expected 9.1.0.0 to be able to run
bundle exec cucumber
without error. 9.0.5.0 with same gems works OK.Actual Behavior
JRuby 9.1.0.0 runs the rspec suite fine, but errors with
Gem::Exception: can't find executable bundle
on Travis. Runs fine on Mac OS X. JRuby 9.0.5.0 with same gems works fine on Travis.The text was updated successfully, but these errors were encountered: