You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Naveen Neelakantam <ne...@uiuc.edu> on 2007/01/12 05:45:34 UTC

[classlib][drlvm] help running classlib tests

Can someone walk me through how to properly run the classlib tests  
using drlvm.

I can run them successfully (well, 3 failures) using J9 by following  
the directions here:
http://svn.apache.org/viewvc/harmony/enhanced/classlib/trunk/RUNNING- 
TESTS.txt?view=co

I also tried copying the working_vm/build/lnx_ia32_gcc_debug/deploy/ 
jdk directory into working_classlib/deploy/jdk and then running "ant  
test" but then I get scores of failures and hundreds of errors,  
mostly from javax.swing.

It actually matches the behavior I am seeing in CC:  http:// 
frigga.cs.uiuc.edu:8080

Could these be real errors?  Or do I just have something configured  
incorrectly.

Naveen

Re: [classlib][drlvm] help running classlib tests

Posted by Elena Semukhina <el...@gmail.com>.
Naveen,

to run the classlib tests on drlvm please use the following command:

ant -Dtest.jre.home=$DRLVM_HOME test

where DRLVM_HOME points at e.g.
.../drlvm/trunk/build/lnx_ia32_gcc_debug/deploy/jdk/jre

Elena


On 1/12/07, Naveen Neelakantam <ne...@uiuc.edu> wrote:
>
> Can someone walk me through how to properly run the classlib tests
> using drlvm.
>
> I can run them successfully (well, 3 failures) using J9 by following
> the directions here:
> http://svn.apache.org/viewvc/harmony/enhanced/classlib/trunk/RUNNING-
> TESTS.txt?view=co
>
> I also tried copying the working_vm/build/lnx_ia32_gcc_debug/deploy/
> jdk directory into working_classlib/deploy/jdk and then running "ant
> test" but then I get scores of failures and hundreds of errors,
> mostly from javax.swing.
>
> It actually matches the behavior I am seeing in CC:  http://
> frigga.cs.uiuc.edu:8080
>
> Could these be real errors?  Or do I just have something configured
> incorrectly.
>
> Naveen
>



-- 
Thanks,
Elena

Re: [classlib][drlvm] help running classlib tests

Posted by Vladimir Ivanov <iv...@gmail.com>.
On 1/19/07, Naveen Neelakantam <ne...@uiuc.edu> wrote:

> >
> > Please, uncomment the line 238 (<!--jvmarg arg="-
> > Dhy.test.forkmode=perTest"
> > /-->) in the configuration to do it.
>
> That seems to have done the trick.  I am only getting 1 failure and 1
> error now.



Yes, this mode more stable while each small TestCase were runs in the proper
vm without any history. But it is does not solve problem just hide it :(



> Is there a way to run an individual test manually so that
> I can place the output into a JIRA?


You can run it through the common build targets from the classlib/trunk
directory like:
ant -Dtest.jre.home=<path_to_jre> -Dtest.case=<test_case_name, like
javax.swing.text.AbstractDocumentTest<http://www.harmonytest.org/testapp.do;jsessionid=C8801A28DE8DAA2F397102C697DAE3FF?method=showresult&id=6716456>>
-Dbuild.module=swing test


or through the command line:
<path_to_jre>/bin/java -cp
<path_to_tests,modules\swing\bin\test>:depends\jars\junit_3.8.2\junit.jar:deploy\build\test\support.jar
junit.textui.TestRunner
javax.swing.text.AbstractDocumentTest<http://www.harmonytest.org/testapp.do;jsessionid=C8801A28DE8DAA2F397102C697DAE3FF?method=showresult&id=6716456>


Thanks, Vladimir





> Thanks,
> Naveen
>
>
> >
> >
> > thanks, Vladimir
> >
> >
> >> Naveen
> >>
>
>

Re: [classlib][drlvm] help running classlib tests

Posted by Naveen Neelakantam <ne...@uiuc.edu>.
>> I can run them successfully (well, 3 failures) using J9 by following
>> the directions here:
>> http://svn.apache.org/viewvc/harmony/enhanced/classlib/trunk/RUNNING-
>> TESTS.txt?view=co
>>
>> I also tried copying the working_vm/build/lnx_ia32_gcc_debug/deploy/
>> jdk directory into working_classlib/deploy/jdk and then running "ant
>> test" but then I get scores of failures and hundreds of errors,
>> mostly from javax.swing.
>>
>> It actually matches the behavior I am seeing in CC:  http://
>> frigga.cs.uiuc.edu:8080
>>
>> Could these be real errors?  Or do I just have something configured
>> incorrectly.
>
>
>
> According to log it is seems to be a real problem. Almost all tests  
> failed
> with message:
>
> "java.lang.OutOfMemoryError: Failed to create new thread"
>
>
>
> As workaround to enable new platform and define problem tests you  
> can run
> these tests in the 'perTest' mode for a while (new vm will be  
> started for
> each test).
>
> Please, uncomment the line 238 (<!--jvmarg arg="- 
> Dhy.test.forkmode=perTest"
> /-->) in the configuration to do it.

That seems to have done the trick.  I am only getting 1 failure and 1  
error now.  Is there a way to run an individual test manually so that  
I can place the output into a JIRA?

Thanks,
Naveen


>
>
> thanks, Vladimir
>
>
>> Naveen
>>


Re: [classlib][drlvm] help running classlib tests

Posted by Vladimir Ivanov <iv...@gmail.com>.
On 1/12/07, Naveen Neelakantam <ne...@uiuc.edu> wrote:

> Can someone walk me through how to properly run the classlib tests
> using drlvm.


Without CC it can be run as (from the classlib module):
ant -Dtest.jre.home=<path to jre> test



> I can run them successfully (well, 3 failures) using J9 by following
> the directions here:
> http://svn.apache.org/viewvc/harmony/enhanced/classlib/trunk/RUNNING-
> TESTS.txt?view=co
>
> I also tried copying the working_vm/build/lnx_ia32_gcc_debug/deploy/
> jdk directory into working_classlib/deploy/jdk and then running "ant
> test" but then I get scores of failures and hundreds of errors,
> mostly from javax.swing.
>
> It actually matches the behavior I am seeing in CC:  http://
> frigga.cs.uiuc.edu:8080
>
> Could these be real errors?  Or do I just have something configured
> incorrectly.



According to log it is seems to be a real problem. Almost all tests failed
with message:

"java.lang.OutOfMemoryError: Failed to create new thread"



As workaround to enable new platform and define problem tests you can run
these tests in the 'perTest' mode for a while (new vm will be started for
each test).

Please, uncomment the line 238 (<!--jvmarg arg="-Dhy.test.forkmode=perTest"
/-->) in the configuration to do it.


 thanks, Vladimir


> Naveen
>