-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
b13
Tests might be skipped from execution for various reasons at different stages.
1. The test might be filtered out because it "did not meet platform requirements" or it was problemlisted. These test will not be run by jtreg.
2. And even after the test was launched, it might throw jtreg.SkippedException at runtime. These tests are also considered skipped.
This information can be read from jtreg's text/stat.txt, text/summary.txt and newly added notRun.txt file starting from jtreg v7.5.
In this ticket, we want to enhance "Test summary" to account for the additional information about the tests that were filtered out or were skipped at runtime with the help of jtreg.SkippedException.
1. The test might be filtered out because it "did not meet platform requirements" or it was problemlisted. These test will not be run by jtreg.
2. And even after the test was launched, it might throw jtreg.SkippedException at runtime. These tests are also considered skipped.
This information can be read from jtreg's text/stat.txt, text/summary.txt and newly added notRun.txt file starting from jtreg v7.5.
In this ticket, we want to enhance "Test summary" to account for the additional information about the tests that were filtered out or were skipped at runtime with the help of jtreg.SkippedException.
- causes
-
-
- Resolved
-
- is blocked by
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8354510 Skipped gtest cause test failure
-
- Resolved
-
-
-
- Closed
-
- links to
-
Commit(master)
openjdk/jdk/2019f445
-
Review(master)
openjdk/jdk/22245
(2 links to)