Closed olleolleolle closed 7 years ago
thanks, unfortunately the specs do not boot - could you maybe try resolving the rspec compatibility issues?
@kares (Will jruby-18mode remain a requirement?)
@olleolleolle do not see why the requirements should change due travis-ci ... only if there was more work
also please keep the new failures at minimum :)
[!] There was an error parsing `Gemfile`: There are multiple gemspecs at /home/travis/build/cowboyd/therubyrhino. Please use the :name option to specify which one should be used. Bundler cannot continue.
# from /home/travis/build/cowboyd/therubyrhino/Gemfile:3
# -------------------------------------------
#
> gemspec
#
# -------------------------------------------
@kares This is me trying to get the gemspec :name => 'therubyrhino'
invocation to work. Update: This was just me being confused.
This was the error that jruby-9.1.8.0 reported.
[!] There was an error parsing `Gemfile`:
[!] There was an error while loading `therubyrhino.gemspec`: . Bundler cannot continue.
. Bundler cannot continue.
# from /home/travis/build/cowboyd/therubyrhino/Gemfile:3
# -------------------------------------------
#
> gemspec :name => "therubyrhino"
#
# -------------------------------------------
(9.1.7.0 can run bundle exec rake
on my OS X machine.)
There's code where Bundler tries to parse out useful descriptive lines from the backtrace.
This may fail on JRuby 9.1.8.0 with a ~dramatic bang~ whimper - where Bundler is unable to find anything that relates to the package at hand in the backtrace.
I think the NPE has been introduced along the way with a commit (maybe a rhino.jar upgrade). code has been always a little edgy on cases, but those features are very unlikely to be used at all. I'm fine to merge this as is since it now at least runs the specs on CI.
@kares Squashed change to a single commit.
@olleolleolle Thanks!
This WIP PR tries to update the builds so that they run on the supported platforms.
JRUBY_OPTS=--debug
Issues we ran into:
Observations: