When a junit or testng test is run, jtreg prints the summary of that test execution. For example:
For testng:
test Test.alwaysFail(): failure [36ms]
...
test Test.alwaysPass(): success [0ms]
...
test Test.alwaysSkip(): skip [2ms]
For junit:
STARTED ExpSwitchNestingTest::testEswitch 'testEswitch()'
SUCCESSFUL ExpSwitchNestingTest::testEswitch 'testEswitch()' [11130ms]
STARTED ExpSwitchNestingTest::testBreakExpressionLabelDisambiguation 'testBreakExpressionLabelDisambiguation()'
SUCCESSFUL ExpSwitchNestingTest::testBreakExpressionLabelDisambiguation 'testBreakExpressionLabelDisambiguation()' [127ms]
...
Right now these log messages don't associate a timestamp with them, which sometimes makes it difficult to correlate with test failures or timeouts when investigating such issues. It would be good to include the timestamp with each of these summary logs.
For testng:
test Test.alwaysFail(): failure [36ms]
...
test Test.alwaysPass(): success [0ms]
...
test Test.alwaysSkip(): skip [2ms]
For junit:
STARTED ExpSwitchNestingTest::testEswitch 'testEswitch()'
SUCCESSFUL ExpSwitchNestingTest::testEswitch 'testEswitch()' [11130ms]
STARTED ExpSwitchNestingTest::testBreakExpressionLabelDisambiguation 'testBreakExpressionLabelDisambiguation()'
SUCCESSFUL ExpSwitchNestingTest::testBreakExpressionLabelDisambiguation 'testBreakExpressionLabelDisambiguation()' [127ms]
...
Right now these log messages don't associate a timestamp with them, which sometimes makes it difficult to correlate with test failures or timeouts when investigating such issues. It would be good to include the timestamp with each of these summary logs.
- links to
-
Commit(master) openjdk/jtreg/470718a0
-
Review(master) openjdk/jtreg/286