RE: Re: [jruby-dev] Re: [jruby-user] JRuby 1.1.3 by end of week...Nominate problems here

Ruby JRuby
1

Will the release still be executed this week? I can’t wait to download
it.

regards

2

I’m having problems getting the current trunk to run all the tests.
Here’s
my setup:arthman:jruby jjathman$ java -version
java version “1.6.0_05”
Java™ SE Runtime Environment (build 1.6.0_05-b13-120)
Java HotSpot™ 64-Bit Server VM (build 1.6.0_05-b13-52, mixed mode)
arthman:bin jjathman$ ./jruby -v
jruby 1.1.3-dev (ruby 1.8.6 patchlevel 114) (2008-07-17 rev 7204)
[x86_64-java]

Looks like the tests don’t like a “server” JVM.

run-junit-compiled:
[echo] compile=JIT, jit.threshold=0, jit.max=-1, objectspace=true
threadpool=false reflection=false version=ruby1_8
[junit] Testsuite: org.jruby.test.ScriptTestSuite
[junit] Tests run: 78, Failures: 0, Errors: 0, Time elapsed: 31.296
sec
[junit]
[junit] Testsuite: org.jruby.test.BFTSTestSuite
[junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 5.756
sec
[junit]
[junit] Testsuite: org.jruby.test.JRubyTestSuite
[junit] Failure:
[junit] test_client_vm_option(TestCommandLineSwitches)
[/Users/jjathman/jruby/./test/test_command_line_switches.rb:236]:
[junit] <“hotspot 64-bit server compiler”> expected to be =~
[junit] </client/>.
[junit] )
[junit] Tests run: 16, Failures: 1, Errors: 0, Time elapsed: 25.68
sec
[junit]
[junit] Testcase:
test_command_line_switches(org.jruby.test.TestUnitTestSuite$ScriptTest):
FAILED
[junit] Faults encountered running test/test_command_line_switches,
complete output follows:
[junit] Failure:
[junit] test_client_vm_option(TestCommandLineSwitches)
[/Users/jjathman/jruby/./test/test_command_line_switches.rb:236]:
[junit] <“hotspot 64-bit server compiler”> expected to be =~
[junit] </client/>.
[junit]
[junit] junit.framework.AssertionFailedError: Faults encountered
running
test/test_command_line_switches, complete output follows:
[junit] Failure:
[junit] test_client_vm_option(TestCommandLineSwitches)
[/Users/jjathman/jruby/./test/test_command_line_switches.rb:236]:
[junit] <“hotspot 64-bit server compiler”> expected to be =~
[junit] </client/>.
[junit]
[junit] at
org.jruby.test.TestUnitTestSuite$ScriptTest.runTest(TestUnitTestSuite.java:206)
[junit]
[junit]

Not sure when this started.

Joe

On Wed, Jul 16, 2008 at 9:30 PM, Charles Oliver N. <

3

Yes…we’ve almost got all our 1.1.3-marked bugs completed, giving us
tomorrow to sanity check everything and push a release, or push to
friday if we find anything.

So anyone interested in helping with sanity checking…pull source
tomorrow and start hitting it.

Partogi, Joshua wrote:

Subject: [jruby-user] Re: [jruby-dev] Re: [jruby-user] JRuby 1.1.3 by
That’s pretty much all there is to it. We provide NB and Eclipse project
you are not the intended recipient, you must not use or disseminate the
information. If you have received this email in error, please
immediately notify me by “Reply” command and permanently delete the
original and any copies or printouts thereof. Although this email and
any attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it is
virus free and no responsibility is accepted by American International
Group, Inc. or its subsidiaries or affiliates either jointly or
severally, for any loss or damage arising in any way from its use.

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
4

Joseph A. wrote:

I’m having problems getting the current trunk to run all the tests.
Here’s my setup:
arthman:jruby jjathman$ java -version
java version “1.6.0_05”
Java™ SE Runtime Environment (build 1.6.0_05-b13-120)
Java HotSpot™ 64-Bit Server VM (build 1.6.0_05-b13-52, mixed mode)
arthman:bin jjathman$ ./jruby -v
jruby 1.1.3-dev (ruby 1.8.6 patchlevel 114) (2008-07-17 rev 7204)
[x86_64-java]

Ahh that test is still a little flaky. Comment out for now…I think we
may have to find a better way to check if it’s the server compiler or
not.

  • Charlie

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
5

Passes for me too now. Thanks for the fix. Glad I could help.
Joe

On Thu, Jul 17, 2008 at 9:13 AM, Vladimir S. [email protected]

6

Hi Joseph,

Thanks for the report!

I bit of background: We had a regression some time ago when the
command line options for setting Client/Server VM were not working, so
I added those regressions tests to make sure it won’t happen again.

But, in case of x64 JVM, there is no client VM at all, only the server
one, hence the test failure, since the test expects the client VM.

I’ve fixed the tests and pushed them to the repository already.

Meanwhile, when running the tests with JDK 6 x64, there were some
other bugs discovered and filed (JRUBY-2817, JRUBY-2818, JRUBY-2819,
JRUBY-2820), and the tests adjusted.

With the latest trunk, ‘ant test’ passes for me now.

Thanks,
–Vladimir

On Thu, Jul 17, 2008 at 7:13 AM, Joseph A. [email protected]
wrote:

Looks like the tests don’t like a “server” JVM.
[junit] Failure:
[junit] Faults encountered running test/test_command_line_switches,
[junit] test_client_vm_option(TestCommandLineSwitches)
Joe

Sent: Thursday, July 17, 2008 2:20 AM
cd jruby

subsidiaries or affiliates either jointly or severally, for any loss or

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email