From vitaly.provodin at jetbrains.com Thu Jun 1 03:08:28 2017 From: vitaly.provodin at jetbrains.com (Vitaly Provodin) Date: Thu, 1 Jun 2017 10:08:28 +0700 Subject: jtreg adds some postfixes into test names In-Reply-To: <3f03b380-b554-76da-5ee4-c0acff826e39@oracle.com> References: <97EA89AE-E6F8-49AB-8092-9F427EE06681@jetbrains.com> <3f03b380-b554-76da-5ee4-c0acff826e39@oracle.com> Message-ID: Hi Jon, Thanks for your reply. Unfortunately, I am not sure it is that case your wrote. My particular case is the file containing one test description (one tag @test). The test was taken from http://hg.openjdk.java.net/jdk9/dev/jdk/file/148a2cbe49a4/test/java/awt/Focus/AutoRequestFocusTest/AutoRequestFocusSetVisibleTest.java and it was not changed. $ cat test/java/awt/Focus/AutoRequestFocusTest/AutoRequestFocusSetVisibleTest.java | grep "@test" @test I also tried to write in description something like $ cat test/java/awt/Focus/AutoRequestFocusTest/AutoRequestFocusSetVisibleTest.java | grep "@test" @test test description in both cases there is only one tag @test and both cases produce the same result: ./jtreg/bin/jtreg -exclude:test/jbProblemsList.txt -ignore:quiet -v -a -xml -testjdk:jbsdk/jdk/Contents/Home test/java/awt/Focus/AutoRequestFocusTest/AutoRequestFocusSetVisibleTest.java XML output to /Users/builduser/9d35cf148e807375/JTwork runner starting test: java/awt/Focus/AutoRequestFocusTest/AutoRequestFocusSetVisibleTest.java#id0 runner finished test: java/awt/Focus/AutoRequestFocusTest/AutoRequestFocusSetVisibleTest.java#id0 Failed. Execution failed: `main' threw exception: TestFailedException: Test failed: the window shouldn't gain focus but it did! Test results: failed: 1 Report written to /Users/builduser/9d35cf148e807375/JTreport/html/report.html Results written to /Users/builduser/9d35cf148e807375/JTwork Error: Some tests failed or other problems occurred. Thanks, Vitaly > On 31 May 2017, at 22:11, Jonathan Gibbons wrote: > > Test names are never changed during test execution. > Postfixes, as you call them, are added when the test is read when you have multiple test descriptions (comments beginning @test) in the same file. > They've always been added for the 2nd and subsequent test descriptions in a file; the recent change is to add them for the first test in a file when the file has multiple tests. This is for uniformity and to be able to disambiguate between specifying "all the tests in a file" vs. "the first test in a file." > > Note that putting multiple test descriptions in a single file has never been formally supported, because of the potential ambiguity that was (finally) resolved by the recent change. > -- Jon > > On 5/30/17 8:06 PM, Vitaly Provodin wrote: >> Hi all, >> >> Running JDK regression tests via jtreg I detected that names of some tests can be changed during test execution. Namely, some postfix is added at the end of test name like follows: >> ===================================8<------------------------------------------------------------- >> #Mon May 29 18:56:12 MSK 2017 >> #-----testdescription----- >> $file=/opt/buildAgent/work/9d35cf148e807375/test/java/awt/Focus/AutoRequestFocusTest/AutoRequestFocusSetVisibleTest.java >> $root=/opt/buildAgent/work/9d35cf148e807375/test >> author=anton.tarasov\: area\=awt.focus >> id=id0 >> keywords=bug6187066 >> library=../../regtesthelpers >> run=USER_SPECIFIED build Util\nUSER_SPECIFIED main AutoRequestFocusSetVisibleTest\n >> source=AutoRequestFocusSetVisibleTest.java >> title=Tests the Window.autoRequestFocus property for the Window.setVisible() method. >> >> #-----environment----- >> >> #-----testresult----- >> compileJDK=/Library/Java/JavaVirtualMachines/jdk1.8.0_111.jdk/Contents/Home >> description=file\:/opt/buildAgent/work/9d35cf148e807375/test/java/awt/Focus/AutoRequestFocusTest/AutoRequestFocusSetVisibleTest.java\#id0 >> elapsed=7463 0\:00\:07.463 >> end=Mon May 29 18\:56\:12 MSK 2017 >> environment=regtest >> ===================================8> >> And jtreg output: >> runner starting test: java/awt/Focus/AutoRequestFocusTest/AutoRequestFocusSetVisibleTest.java#id0 >> runner finished test: java/awt/Focus/AutoRequestFocusTest/AutoRequestFocusSetVisibleTest.java#id0 >> Failed. Execution failed: `main' threw exception: TestFailedException: Test failed: the window shouldn't gain focus but it did! >> >> As you can see the test java/awt/Focus/AutoRequestFocusTest/AutoRequestFocusSetVisibleTest.java became java/awt/Focus/AutoRequestFocusTest/AutoRequestFocusSetVisibleTest.java\#id0 ("\#id0? was added). >> Please note the issue was observed intermittently. >> >> The matter was that this test was included into my exclude list, nevertheless it was executed because of this postfix (most probably new test name does not correspond to the name included into exclude list). >> I looked through documentation on jtreg but could not find any explanations for this behaviour. >> My suspicious was concurrent execution of the tests but I could not find any symptoms confirming that. >> >> My original intentions was to exclude some tests from test runs but I could not do it because of this issue. I tried to use regular expressions in test names adding them into exclude list but it did not help. >> >> Here is command line used to start test runs: >> >> $ jtreg -exclude:test/jbProblemsList.txt -ignore:quiet -v -a -xml -compilejdk:'%env.JDK_18_x64%' -testjdk:'%jtreg.testjdk%' -timeoutFactor:2 test/java/awt || echo 'Execution complete? >> >> Could you please help me in resolving the following questions? why does jtreg add some postfixes? how can I exclude such tests from test runs? >> >> >> Thanks in advance, >> Vitaly >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bysanik at amazon.com Tue Jun 13 19:17:12 2017 From: bysanik at amazon.com (Bysani, Keerthana) Date: Tue, 13 Jun 2017 19:17:12 +0000 Subject: Can't init module exports: unexpected exception: java.lang.ClassNotFoundException: java.lang.JTRegModuleHelper Message-ID: Hi, I recently ran the hotspot test suite on an OpenJDK Tree with a custom GC on May 30th and the stats show that around a 150 tests errored out. When I ran the same tests again a few days back, the results reported that around 750 tests errored out because of: Can't init module exports: unexpected exception: java.lang.ClassNotFoundException: java.lang.JTRegModuleHelper This is the script I ran for testing: #!/bin/sh export JT_JAVA=/home/test/OpenJDKTrees/openjdk9-05-19/build/linux-x86_64-normal-server-slowdebug/images/jdk /home/test/jtreg/bin/jtreg -g -jdk:$JT_JAVA -agentvm -automatic -verbose:summary -w build/jtreg/work -r build/jtreg/report -javaoptions:"-\ XX:+UseRtGC -XX:-UseCompressedOops -Xms256m -d64" hotspot/test Can someone please let me know where Im going wrong? Thanks and Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From bysanik at amazon.com Thu Jun 29 19:04:20 2017 From: bysanik at amazon.com (Bysani, Keerthana) Date: Thu, 29 Jun 2017 19:04:20 +0000 Subject: Cannot find Jasm & Jcoder Message-ID: <71C1D4CE-2188-4CB7-8491-7F881D5C69D5@amazon.com> Hi, When I execute the hotspot test suite on the Openjdk9 tree in SerialGC Mode, Around 20 to 30 tests error out because they couldn?t find jcoder or jasm modules. What can I do to include them? How should I include them? Also most tests error out because the native path to the code cannot be found. How do I explicitly provide the path to the native code using ?nativepath? Any tips and pointers on this will help me a lot. Regards, Keerthana Bysani -------------- next part -------------- An HTML attachment was scrubbed... URL: From bysanik at amazon.com Thu Jun 29 19:08:46 2017 From: bysanik at amazon.com (Bysani, Keerthana) Date: Thu, 29 Jun 2017 19:08:46 +0000 Subject: Is it normal behavior for tests to timeout Message-ID: Hi, I was executing the hotspot test suite(hotspot/test) on the openjdk9 build with the Serial Garbage Collector. Test Script -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- #!/bin/sh export JT_JAVA=/home/test/openjdk9-new/build/linux-x86_64-normal-server-slowdebug/images/jdk /home/test/jtreg/bin/jtreg -g -jdk:$JT_JAVA -agentvm -automatic -verbose:summary -w build/jtreg/work -r build/jtreg/report -javaoptions:"-XX:+UseSerialGC -XX:-UseCompressedOops -Xms256m -d64" hotspot/test -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- A report of all tests that failed and errored out was generated once the tests completed. (101 failed and 130 errored out) I would be happy to send the reports to anyone who is interested in this problem. Is it normal for the SerialGC to fail / timeout for so many tests? If not, what am I doing wrong? Since I am using this as a benchmark for a custom garbage collector , I wanted to check if I was getting precise results. Thanks and regards, Keerthana -------------- next part -------------- An HTML attachment was scrubbed... URL: