CODETOOLS-7903323: Review and improve performance of jtreg reporting.

[jonathan-gibbons]

Please review a medium simple update to address the annoying delay between the last test being executed and jtreg exiting.

The delay is due to writing the report, a side-effect of which is to scan the entire test-suite, to determine which tests have been executed.

It is not easy/simple to optimize that default; instead, a new report mode is added, that reports on all the tests in the test files and groups given on the command line -- ignoring any additional filters such as the status filter, keyword filter and exclude list filter. As such, it has more "common-sense" semantics when rerunning tests with -status:fail.

There were no existing tests for the -report option. Tests have been added for all flavors of the -report option.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• CODETOOLS-7903323: Review and improve performance of jtreg reporting.

Reviewers

• Iris Clark (@irisclark - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jtreg pull/125/head:pull/125
$ git checkout pull/125

Update a local copy of the PR:
$ git checkout pull/125
$ git pull https://git.openjdk.org/jtreg pull/125/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 125

View PR using the GUI difftool:
$ git pr show -t 125

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jtreg/pull/125.diff

[bridgekeeper]

👋 Welcome back jjg! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[mlbridge]

Webrevs

• 00: Full (e93e5216)

[openjdk]

@jonathan-gibbons This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

7903323: Review and improve performance of jtreg reporting.

Reviewed-by: iris

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[jonathan-gibbons]

/integrate

[openjdk]

Going to push as commit de2c216.
Since your change was applied there has been 1 commit pushed to the master branch:

• 66efe4b: 7903329: Trace reasons to recompile extra property definition files

Your commit was automatically rebased without conflicts.

[openjdk]

@jonathan-gibbons Pushed as commit de2c216.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.