-
Enhancement
-
Resolution: Fixed
-
P4
-
11, 17, 21
-
b05
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8299734 | na | Aleksey Shipilev | P4 | Closed | Not an Issue |
This should help to speed up tests significantly. Currently, if we run "make test" with a subset of tests, JTReg would still read the entirety of test root to report on tests that were not run. Even with current suite of tests it gets expensive. If you add more tests to suite -- for example, mounting a large test archive like pre-generated fuzzer tests -- it starts to take a lot of time.
The reasonable default for older jtreg is `-report:executed`. My own CI -- that has millions of tests mounted in `test/` -- was running with `JTREG="OPTIONS=-report:executed"` for years now.CODETOOLS-7903323 provides a new reporting option, `-report:files`, which makes this whole business easier. This requires new jtreg.
The reasonable default for older jtreg is `-report:executed`. My own CI -- that has millions of tests mounted in `test/` -- was running with `JTREG="OPTIONS=-report:executed"` for years now.
- backported by
-
JDK-8299734 [REDO] make test should report only on executed tests
- Closed
- clones
-
JDK-8294142 make test should report only on executed tests
- Closed
- is blocked by
-
JDK-8298178 Update to use jtreg 7.1.1
- Resolved
- relates to
-
CODETOOLS-7903323 Review and improve performance of jtreg reporting.
- Resolved
-
CODETOOLS-7903331 jtreg fails with StringIndexOutOfBoundsException: Index -1 out of bounds for length 0
- Resolved
-
CODETOOLS-7903318 Make -report:executed the default
- Closed
(1 relates to, 2 links to)
There are no Sub-Tasks for this issue.