RFR(S) : CODETOOLS-7902810 : allow test/driver to examine problem lists

[Jonathan Gibbons]

For discussion ...

The set of env variables and system properties does seem to be growing 
without bound.

Should we be looking at alternative mechanisms, such as an external 
file, for some of these values, especially those which are not 
test-specific?

-- Jon

On 12/9/20 11:11 AM, Igor Ignatyev wrote:
> http://cr.openjdk.java.net/~iignatyev/CODETOOLS-7902810/webrev.00/
>> 28 lines changed: 27 ins; 0 del; 1 mod;
> Hi all,
>
> could you please review this small patch which adds `test.exclude.files` /   `TESTEXCLUDEFILES and `test.match.files` / `TESTMATCHFILES` java properties / env. variables which contain list of paths to files specified via `-exclude:` and `-match:` respectively?
>
> from JBS:
>> some of our jtreg tests are actually wrappers around 3rd party tests. and sometimes one wrapper runs more than one test (due to performance or other restrictions). as with any other tests, we might need to temporarily exclude some of these tests from execution, and using regular jtreg ProblemList files (specified by -exclude: option) is the most natural way to do that. unfortunately, jtreg doesn't provide a way for tests to know which files were specified by -exclude: option, let alone a way to determine if certain tests should be excluded (based on names and current OS/arch).
>
> JBS: https://bugs.openjdk.java.net/browse/CODETOOLS-7902810
> webrev: http://cr.openjdk.java.net/~iignatyev/CODETOOLS-7902810/webrev.00/
>
> Thanks,
> -- Igor
>