7903883: --verify-exclude test existence and format checks are broken

[LudwikJaniuk]

The way this feature selected "the full set of tests" was actually getting "the set of tests to be run". But often, we run some subset through either specifying test files, folders, or groups. Our problemlist files will still have entries for other tests we were not running right now.

As a solution, --verify-exclude needs to compute the maximal set of tests that could be run for all test suites that any of the tests being run are a part of. I've implemented this by creating a dummy testmanager and passing no parameters to it.

Additionally, the regex for problemlist format had a typo.

---

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-7903883: --verify-exclude test existence and format checks are broken (Bug - P4)

Reviewers

• Christian Stein (@sormuras - Committer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 236

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back lujaniuk! 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.

[openjdk]

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

[mlbridge]

Webrevs

• 01: Full - Incremental (fd5e203f)
• 00: Full (65869e8b)

[sormuras]

Looks good so far, left some requests regarding a TODO comment and optional verbose output.

[sormuras]

Suggested change

// TODO We know set of suites here, could save/do dummy

Please don't add TODO comments — just do it, or don't.

[LudwikJaniuk]

Thank you for reviewing @sormuras. I agree with all your comments and have addressed them. I chose to put the test names behind -va because that's a huuuuge list for the jdk.

[sormuras]

Looks good to me.