P4
Since CODETOOLS-7904015, jtreg can check the correctness of exclude files (problem lists).
However, it is common to have exclude lists which include tests that are specified as relative several (arbitrary and unstated) test roots. This makes it easy to apply this exclude file (e.g. "exclude these tests when running with aot" and it can exclude both jdk and hotspot tests, for instance). This works just fine and as intended.
But when running with --verify-exclude, and only one of these test roots (e.g. hotspot), then it will complain about the unknown tests in the jdk test root, and vice versa.
This behavior makes it impossible to apply --verify-exclude on a wide scale in the JDK.
The best solution is probably to be able to specify additional "known test roots" to jtreg, that is used when locating files during exclude verification, but not for picking up any tests.
However, it is common to have exclude lists which include tests that are specified as relative several (arbitrary and unstated) test roots. This makes it easy to apply this exclude file (e.g. "exclude these tests when running with aot" and it can exclude both jdk and hotspot tests, for instance). This works just fine and as intended.
But when running with --verify-exclude, and only one of these test roots (e.g. hotspot), then it will complain about the unknown tests in the jdk test root, and vice versa.
This behavior makes it impossible to apply --verify-exclude on a wide scale in the JDK.
The best solution is probably to be able to specify additional "known test roots" to jtreg, that is used when locating files during exclude verification, but not for picking up any tests.