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).