P4
The comment below was made in PR https://github.com/openjdk/jdk/pull/24860 (see https://github.com/openjdk/jdk/pull/24860#issuecomment-2830009985). From the comment it seems that the visibility of tests not run in the CI pipeline due to @requires should be raised to facilitate auditing test runs.
"A general comment on this approach of running tests selectively on an OS via @requires It is all cool and dandy, but this has implications on the visibility of the test not being run. It will be added to the jtreg "not run" list. When running test locally that's fine, this is easily seen in the jtreg report, but when run in the test frameworks CI pipeline, this "not run " visibility is obscured. Thus when doing test run audit of a jobs, requires a bit more effort to locate test that have not been run.
An alternative practice has been to throw a SkippedException and this is more easily observed in a pipeline job's results, as the SkippedException are part of all results, and jtreg now reports Skipped tests in its summary."
"A general comment on this approach of running tests selectively on an OS via @requires It is all cool and dandy, but this has implications on the visibility of the test not being run. It will be added to the jtreg "not run" list. When running test locally that's fine, this is easily seen in the jtreg report, but when run in the test frameworks CI pipeline, this "not run " visibility is obscured. Thus when doing test run audit of a jobs, requires a bit more effort to locate test that have not been run.
An alternative practice has been to throw a SkippedException and this is more easily observed in a pipeline job's results, as the SkippedException are part of all results, and jtreg now reports Skipped tests in its summary."