Alexandr,
System.exit(exitStatus) in my test is called only by child JVM process,
JTREG does not know about it.
Test passes in my case.
We had already the same discussion with Sergey Bylokhov (see below).
Thanks,
Konstantin
On 17-Feb-14 15:04, Alexander Scherbatiy wrote:
I use the jtreg 4.1 fcs b05 and it fails the test with System.exit()
with zero and non-zero exit value:
------- test.java -------------------------
/**
* @test
* @bug 8000000
* @run main test
*/
public class test {
public static void main(String[] args) throws Exception {
int exitStatus = 0;
System.out.println("Exit status: " + exitStatus);
System.exit(exitStatus);
}
}
--------------------------------
TEST RESULT: Failed. Unexpected exit from test [exit code: 0]
Is your test passed in this case?
Thanks,
Alexandr.
On 2/13/2014 3:52 PM, Konstantin Shefov wrote:
Reminder
On 10-Feb-14 11:33, Konstantin Shefov wrote:
Please, review this test fix.
The test blocks automated test execution, so should be fixed.
Thanks
-Konstantin
On 06-Feb-14 17:55, Sergey Bylokhov wrote:
Thanks.
Then the fix looks good.
On 06.02.2014 17:53, Konstantin Shefov wrote:
On 06-Feb-14 17:49, Konstantin Shefov wrote:
Sergey,
This System.exit will never be seen by jtreg, more than that, this
test already has system.exit and will not work without it.
System.exit is invoked by child vm, child vm is NOT controlled by
JTREG at all.
Konstantin
On 06-Feb-14 17:21, Sergey Bylokhov wrote:
Hi, Konstantin.
The tests should not use System.exit() , it can be forbidden in
some modes of jtreg.
On 06.02.2014 17:03, Konstantin Shefov wrote:
Hi all,
please review the fix
http://cr.openjdk.java.net/~kshefov/8017456/webrev.00
for
https://bugs.openjdk.java.net/browse/JDK-8017456
Test hangs on windows if test frames are covered by a window of
some other app.
Thanks,
Konstantin
