[jruby-dev] [jira] (JRUBY-7031) Failing tests kill RSpec in Nailgun
Stephen Eley created JRUBY-7031 Failing tests kill RSpec in Nailgun Issue Type: Bug Affects Versions: JRuby 1.7.1 Assignee: Unassigned Components: Application Error, Extensions Created: 13/Dec/12 1:24 PM Description: When passing the RSpec invocation to Nailgun's JVM, any failing spec causes the process to hard crash with a SystemExit after completion. To reproduce the bug, the Nailgun server is first started up as follows: $ jruby --ng-server & I created two trivial specs to illustrate the error: simple_pass.rb describe "Simple Pass" do it "should pass" do true.should be_true end end simple_fail.rb describe "Simple Fail" do it "should fail" do true.should be_false end end Running the passing spec with the --ng option to pass to Nailgun works fine: $ jruby --ng -S rspec simple_pass.rb . Finished in 0.004 seconds 1 example, 0 failures $ echo $? 0 However, running the failing spec ends with an abnormal exit: $ jruby --ng -S rspec simple_fail.rb F Failures: 1) Simple Fail should fail Failure/Error: true.should be_false expected: false value got: true # ./simple_fail.rb:3:in `(root)' Finished in 0.005 seconds 1 example, 1 failure Failed examples: rspec ./simple_fail.rb:2 # Simple Fail should fail org.jruby.exceptions.RaiseException: (SystemExit) exit $ echo $? 131 Running without the *--ng* option (i.e., spawning a new JVM instead of using Nailgun's) caused the second example to exit cleanly, without the org.jruby.exceptions.RaiseException: (SystemExit) exit output and with a 0 exit code. This behavior is consistent in more complex suites, and also occurs when running RSpec within Guard. (The desire to speed things up in Guard is in fact why I wanted to use Nailgun.) The inconsistent behavior when not passing to Nailgun is why my first guess was that this was some sort of RSpec bug; I've raised an issue on their Github project as well, but the maintainer said he would have to talk to the JRuby guys. Thanks very much for your time. Environment: * JRuby 1.7.1 (under rbenv using ruby-build 20121204) * rspec (2.12.0) * rspec-core (2.12.1) * rspec-expectations (2.12.0) * rspec-mocks (2.12.0) Project: JRuby Labels: nailgun rspec Priority: Major Reporter: Stephen Eley This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jruby-dev] [jira] (JRUBY-7032) Time#strftime %3N doesn't limit sub-seconds to 3 digits
Tim Hayman created JRUBY-7032 Time#strftime %3N doesn't limit sub-seconds to 3 digits Issue Type: Bug Affects Versions: JRuby 1.7.1 Assignee: Unassigned Components: Core Classes/Modules Created: 13/Dec/12 1:29 PM Description: >jruby -e "puts Time.now.strftime('%3N')" 64500 >jruby -e "puts Time.now.strftime('%2N')" 68200 In fact, it always gives 9 digits, regardless of the length value. The fix for JRUBY-6964 changed the formatting to use String.format (from the method formatTruncate) but String.format won't truncate a string that is too long. Project: JRuby Priority: Major Reporter: Tim Hayman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jruby-dev] [jira] (JRUBY-7033) yielding from fiber fails when running jruby with --debug
Tim Olsen created JRUBY-7033 yielding from fiber fails when running jruby with --debug Issue Type: Bug Affects Versions: JRuby 1.7.1 Assignee: Unassigned Components: Core Classes/Modules Created: 13/Dec/12 5:13 PM Description: Given the following file fiber_test.rb: fiber = Fiber.new do Fiber.yield 1 2 end puts fiber.resume puts fiber.resume Running it with --debug fails: $ ruby --debug fiber_test.rb NoMethodError: undefined method `yield' for Fiber:Class (root) at fiber_test.rb:2 whereas running without --debug succeeds: $ ruby fiber_test.rb 1 2 Environment: jruby-head commit d80b18fbaec0df59276f5ec2b7ce3de92cce63ce jruby 1.7.2.dev (1.9.3p327) 2012-12-13 fff on Java HotSpot(TM) 64-Bit Server VM 1.7.0_07-b10 [darwin-x86_64] Mac OS X 10.7.5 Project: JRuby Priority: Major Reporter: Tim Olsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jruby-dev] [jira] (JRUBY-7034) OpenSSL::X509::StoreError with OpenJDK6/JRuby 1.7.1. Same code works with OpenJDK6/JRuby 1.7.0.preview2 and OracleJDK6/JRuby 1.7.1
Takayuki Okazaki created JRUBY-7034 OpenSSL::X509::StoreError with OpenJDK6/JRuby 1.7.1. Same code works with OpenJDK6/JRuby 1.7.0.preview2 and OracleJDK6/JRuby 1.7.1 Issue Type: Bug Affects Versions: JRuby 1.7.1 Assignee: Unassigned Components: OpenSSL Created: 13/Dec/12 8:49 PM Description: Exception thrown during upgrade of my environment to JRuby 1.7.1 from JRuby 1.7.0.preview2 with exactly same source code. This happens only with OpenJDK at least my environment. The code works with: JRuby 1.7.1 / Oracle JDK 6 (1.6.0_26) / Debian Lenny JRuby 1.7.0.preview2 / OpenJDK 6 (1.6.0_18) / Debian Lenny The code fails with: JRuby 1.7.1 / OpenJDK 6 (1.6.0_18) / Debian lenny OpenSSL::X509::StoreError: setting default path failed: the trustAnchors parameter must be non-empty set_default_paths at org/jruby/ext/openssl/X509Store.java:162 SSLContext at //jruby-1.7.1/lib/ruby/1.9/openssl/ssl-internal.rb:31 SSL at //jruby-1.7.1/lib/ruby/1.9/openssl/ssl-internal.rb:22 OpenSSL at //jruby-1.7.1/lib/ruby/1.9/openssl/ssl-internal.rb:21 (root) at //jruby-1.7.1/lib/ruby/1.9/openssl/ssl-internal.rb:20 require at org/jruby/RubyKernel.java:1027 require at //jruby-1.7.1/lib/ruby/shared/rubygems/custom_require.rb:36 (root) at //jruby-1.7.1/lib/ruby/1.9/openssl.rb:1 require at org/jruby/RubyKernel.java:1027 require at //jruby-1.7.1/lib/ruby/shared/rubygems/custom_require.rb:36 (root) at //jruby-1.7.1/lib/ruby/1.9/openssl.rb:28 require at org/jruby/RubyKernel.java:1027 require at //jruby-1.7.1/lib/ruby/shared/rubygems/custom_require.rb:36 (root) at //jruby-1.7.1/lib/ruby/1.9/net/https.rb:1 require at org/jruby/RubyKernel.java:1027 require at //jruby-1.7.1/lib/ruby/shared/rubygems/custom_require.rb:36 (root) at //jruby-1.7.1/lib/ruby/1.9/net/https.rb:22 require at org/jruby/RubyKernel.java:1027 require at //jruby-1.7.1/lib/ruby/shared/rubygems/custom_require.rb:36 (root) at //gem/gems/google_drive-0.3.1/lib/google_drive/client_login_fetcher.rb:1 require at org/jruby/RubyKernel.java:1027 require at //jruby-1.7.1/lib/ruby/shared/rubygems/custom_require.rb:60 require at //jruby-1.7.1/lib/ruby/shared/rubygems/custom_require.rb:55 (root) at //gem/gems/google_drive-0.3.1/lib/google_drive/client_login_fetcher.rb:4 require at org/jruby/RubyKernel.java:1027 require at //jruby-1.7.1/lib/ruby/shared/rubygems/custom_require.rb:36 (root) at //gem/gems/google_drive-0.3.1/lib/google_drive/session.rb:1 require at org/jruby/RubyKernel.java:1027 (root) at //gem/gems/google_drive-0.3.1/lib/google_drive/session.rb:11 Environment: JRuby 1.7.1 Failed) {quote} java version "1.6.0_18" OpenJDK Runtime Environment (IcedTea6 1.8.10) (6b18-1.8.10-0~lenny2) OpenJDK Client VM (build 14.0-b16, mixed mode, sharing) {quote} Succeed) {quote} java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) Client VM (build 20.1-b02, mixed mode, sharing) {quote} Project: JRuby Priority: Major Reporter: Takayuki Okazaki This message is automatically generated by JIRA. If you think it was