MacOS X 10.7 Lion & Ubuntu 12.04 - JTReg tests failing!

[Balchandra Vaidya]

Hi,

Just back from a vacation and saw this question. My comments are below 
for jtreg tests:

On 03/16/13 01:50 AM, Mani Sarkar wrote:
> Hi,
>
> I ran JTReg tests on my Ubuntu 12.04 and MacOS X 10.7 Lion systems, 
> via the /~/sources/jdk8_tl/test/ folder after installing *jtreg* and 
> setting up the environment with paths settings for jt_home and 
> product_home. I got the below results, although the issues were 
> similar in both environments there are differences between the two 
> across more than one test component.
>
>
> *jdk_lang* *(logs: http://bit.ly/Z97COE)*
> (TEST STATS: name=jdk_lang  run=426  pass=415  fail=11  excluded=5)
> /Failure reasons: Tests failed without specifying any reason, ??? 
> returned!/
> FAILED: java/lang/invoke/AccessControlTest.java
> FAILED: java/lang/invoke/BigArityTest.java
> FAILED: java/lang/invoke/ClassValueTest.java
> FAILED: java/lang/invoke/InvokeGenericTest.java
> FAILED: java/lang/invoke/JavaDocExamplesTest.java
> FAILED: java/lang/invoke/MethodHandlesTest.java
> FAILED: java/lang/invoke/MethodTypeTest.java
> FAILED: java/lang/invoke/PermuteArgsTest.java
> FAILED: java/lang/invoke/PrivateInvokeTest.java
> FAILED: java/lang/invoke/RicochetTest.java
> FAILED: java/lang/invoke/ThrowExceptionsTest.java
>
> /
> These above tests should have passed as per the test results archive!
> /

Above tests require JUnit.  Copy junit.jar into jtreg/lib directory and 
then check
again.

> -----------------------------
>
> There are more packages failing tests on Ubuntu than MacOS, more tests 
> in total have failed and under each component. Should I report these 
> to other report mailing lists as well?
>
> Rory, Balchandra - am I running these tests differently than you are 
> since your test results (test results archive) differs from mine.
>
> I run the tests using the below syntax:
>
> /$ make TEST=<test component name> /
>
> Just to isolate the test failures I ran each test component rather 
> than what people usually do jdk_default, jdk_core and jdk_all. Could 
> you also make the make command failure error messages a bit more 
> verbose and human-friendly so we can figure out whats to start looking 
> at. If I have missed out on config I would love to know.

If you see any test failures with the make target, I suggest, run the failed
tests (group of tests) using jtreg directly.  This will isolate Makefile 
related issues.

Here is the instruction about how I run the tests:
http://bambi.ie.oracle.com/web/openjdk/results-large/docs/howtoruntests.html

You can also run an individual test, for example:
      $ jtreg -verbose:fail java/lang/invoke/AccessControlTest.java

You can run all tests under particular sub-directory, for example:
      $ jtreg -verbose:fail java/lang/invoke



Thanks
Balchandra


>
> Thanks.
>
> Cheers,
> mani
> -- 
> *Twitter:* @theNeomatrix369
> *Blog:* http://neomatrix369.wordpress.com
> *JUG activity:* LJC Advocate (@adoptopenjdk & @adoptajsr programs)
> *Meet-a-Project:* https://github.com/MutabilityDetector
> *Come to Devoxx UK 2013:* http://www.devoxx.com/display/UK13/Home
> */Don't chase success, rather aim for "Excellence", and success will 
> come chasing after you!/*

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20130319/870d037a/attachment.html