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(TM) SE Runtime Environment (build 1.6.0_05-b13-120)
Java HotSpot(TM) 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 Nutter <
[EMAIL PROTECTED]> wrote:
> 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:
>
>> Will the release still be executed this week? I can't wait to download it.
>>
>> regards
>>
>> -----Original Message-----
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
>> Behalf Of Charles Oliver Nutter
>> Sent: Thursday, July 17, 2008 2:20 AM
>> To: [email protected]
>> Cc: [EMAIL PROTECTED]
>> Subject: [jruby-user] Re: [jruby-dev] Re: [jruby-user] JRuby 1.1.3 by end
>> of week...Nominate problems here...
>>
>> I think there's a walkthrough on wiki.jruby.org, but it's pretty simple
>>
>> Prereqs: Ant 1.7, Java 5+, Subversion
>>
>> svn co http://svn.codehaus.org/jruby/trunk/jruby
>> cd jruby
>> ant [jar test spec dist]
>>
>> That's pretty much all there is to it. We provide NB and Eclipse project
>> files, though I don't know anyone that's using Eclipse anymore on the
>> project.
>>
>> And others might recommend some git-based instructions, if you'd like to
>> be able to commit, format-patch, branch and such on your own. We do not
>> (yet) use git as primary repository.
>>
>>
>> IMPORTANT NOTICE:
>> The information in this email (and any attachments) is confidential. If
>> 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
>
>
>
