bump jruby 9.0.0.0-pre2 #702
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 9.0.0.0.pre1-jre: git://github.com/cpuguy83/docker-jruby@3a9e548c1f080e9116c13a8d62bf01ebc2e2c629 9000/jre | ||
| 9.0.0.0: git://github.com/cpuguy83/docker-jruby@0f5ca4efd34cedd56e7e2c7138f98c5e80402c6b 9000/jre | ||
| 9.0.0.0-jre: git://github.com/cpuguy83/docker-jruby@0f5ca4efd34cedd56e7e2c7138f98c5e80402c6b 9000/jre | ||
| 9.0.0.0.pre2: git://github.com/cpuguy83/docker-jruby@540fa78ad4845773b0d9e361fa7f8000161825a1 9000/jre |
There was a problem hiding this comment.
Ah, looks like this one got missed somehow. 😢
Signed-off-by: Brian Goff <cpuguy83@gmail.com>
|
Fixed. |
|
LGTM (jruby/docker-jruby@3a9e548...0f5ca4e) Build test of #702; bf12d7d ( $ url="https://raw.githubusercontent.com/docker-library/official-images/bf12d7dcdc85aa34b1593787216c9c9f767ae019/library/jruby"
$ bashbrew build "$url"
Processing jruby:1.7 ...
Processing jruby:1.7.19 ...
Processing jruby:latest ...
Processing jruby:1.7-jre ...
Processing jruby:1.7.19-jre ...
Processing jruby:1.7-jdk ...
Processing jruby:1.7.19-jdk ...
Processing jruby:1.7-onbuild ...
Processing jruby:1.7.19-onbuild ...
Processing jruby:9.0.0.0 ...
Processing jruby:9.0.0.0-jre ...
Processing jruby:9.0.0.0.pre2 ...
Processing jruby:9.0.0.0.pre2-jre ...
Processing jruby:9.0.0.0-jdk ...
Processing jruby:9.0.0.0.pre2-jdk ...
Processing jruby:9.0.0.0-onbuild ...
Processing jruby:9.0.0.0.pre2-onbuild ...
$ bashbrew list --uniq "$url" | xargs test/run.sh
testing jruby:1.7
'utc' [1/5]...passed
'cve-2014--shellshock' [2/5]...passed
'ruby-standard-libs' [3/5]...passed
'ruby-gems' [4/5]...passed
'ruby-bundler' [5/5]...passed
testing jruby:1.7-jdk
'utc' [1/5]...passed
'cve-2014--shellshock' [2/5]...passed
'ruby-standard-libs' [3/5]...passed
'ruby-gems' [4/5]...passed
'ruby-bundler' [5/5]...passed
testing jruby:1.7-onbuild
'utc' [1/5]...passed
'cve-2014--shellshock' [2/5]...passed
'ruby-standard-libs' [3/5]...passed
'ruby-gems' [4/5]...passed
'ruby-bundler' [5/5]...passed
testing jruby:9.0.0.0
'utc' [1/5]...passed
'cve-2014--shellshock' [2/5]...passed
'ruby-standard-libs' [3/5].../opt/jruby/lib/ruby/stdlib/ripper/core.rb:13: warning: already initialized constant SCANNER_EVENT_TABLE
/opt/jruby/lib/ruby/stdlib/ripper/core.rb:13: warning: already initialized constant PARSER_EVENT_TABLE
/opt/jruby/lib/ruby/stdlib/ripper/core.rb:13: warning: already initialized constant Version
/opt/jruby/lib/ruby/stdlib/ripper/core.rb:13: warning: already initialized constant SCRIPT_LINES__
passed
'ruby-gems' [4/5]...passed
'ruby-bundler' [5/5]...passed
testing jruby:9.0.0.0-jdk
'utc' [1/5]...passed
'cve-2014--shellshock' [2/5]...passed
'ruby-standard-libs' [3/5].../opt/jruby/lib/ruby/stdlib/ripper/core.rb:13: warning: already initialized constant SCANNER_EVENT_TABLE
/opt/jruby/lib/ruby/stdlib/ripper/core.rb:13: warning: already initialized constant PARSER_EVENT_TABLE
/opt/jruby/lib/ruby/stdlib/ripper/core.rb:13: warning: already initialized constant Version
/opt/jruby/lib/ruby/stdlib/ripper/core.rb:13: warning: already initialized constant SCRIPT_LINES__
passed
'ruby-gems' [4/5]...passed
'ruby-bundler' [5/5]...passed
testing jruby:9.0.0.0-onbuild
'utc' [1/5]...passed
'cve-2014--shellshock' [2/5]...passed
'ruby-standard-libs' [3/5].../opt/jruby/lib/ruby/stdlib/ripper/core.rb:13: warning: already initialized constant SCANNER_EVENT_TABLE
/opt/jruby/lib/ruby/stdlib/ripper/core.rb:13: warning: already initialized constant PARSER_EVENT_TABLE
/opt/jruby/lib/ruby/stdlib/ripper/core.rb:13: warning: already initialized constant Version
/opt/jruby/lib/ruby/stdlib/ripper/core.rb:13: warning: already initialized constant SCRIPT_LINES__
passed
'ruby-gems' [4/5]...passed
'ruby-bundler' [5/5]...passed |
|
Those warnings in 9.0.0.0 are ugh, but meh; maybe jruby upstream bugs? |
|
Seems so. |
|
@cpuguy83 are we good to merge here? |
|
Yes, this is a pre-release build afterall :) |
|
LGTM |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.