jtreg cannot be run against a pre-built/downloaded JDK anymore?
jai.forums2013 at gmail.com
Sat Nov 13 08:28:14 UTC 2021
On 13/11/21 12:07 pm, David Holmes wrote:
> On 13/11/2021 3:37 pm, Jaikiran Pai wrote:
>> I got past this with an extensive workaround for now. I moved/copied
>> that test case java file outside of the JDK source tree, then created
>> a new/custom TEST.ROOT which is very minimal and has no reference to
>> whitebox for bootlibs, then made sure the jtwork directory is also
>> outside of the JDK source tree (so that the test is compiled afresh)
>> and then ran that test. That helped, but it's only for this test
>> since its requirements in the test are very minimal. I don't see a
>> way to get past this if I have to run the wider range of jtreg tests
>> that reside in the JDK source tree against a pre-built/downloaded
>> Java 17 or any previous versions.
> Basically you're not supposed to do that.
I wasn't aware of that. I used to use this method to selectively run
newly added jtreg tests against different downloaded versions of JDK and
assumed it was a supported usecase.
Thanks everyone for the inputs.
More information about the jtreg-use