| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8056323 | emb-9 | Christian Tornqvist | P3 | Resolved | Fixed | b29 |
This idea came out of a meeting between Coleen, Christian, Misha and George today.
We should:
- look at the existing jt-reg runtime tests and identify a subset that would be most beneficial to ran as part of every check-in
- the tests should be effective and cover critical areas
- the tests should not increase the JPRT push test execution by more than 10% (more or less?)
- once identified and exercises, they should be added to the JPRT push configuration (jprt.properties AFAIK)
- recommend that other HotSpot groups do the same
We should:
- look at the existing jt-reg runtime tests and identify a subset that would be most beneficial to ran as part of every check-in
- the tests should be effective and cover critical areas
- the tests should not increase the JPRT push test execution by more than 10% (more or less?)
- once identified and exercises, they should be added to the JPRT push configuration (jprt.properties AFAIK)
- recommend that other HotSpot groups do the same
- backported by
-
JDK-8056323 [TESTBUG] JT-Reg Runtime tests to be run as part of JPRT submit job
-
- Resolved
-
- relates to
-
JDK-8064799 [TESTBUG] jtreg Serviceability tests to be run as part of JPRT submit job
-
- Resolved
-