building the jtreg using jdk11.0.18

[Langer, Christoph]

Hi,

in the mid term we should aim for higher jtreg. However, looks like it has a few prerequisites. E.g. start with https://bugs.openjdk.org/browse/JDK-8289798.

For now, we need https://github.com/openjdk/jtreg/commit/dffb1eeafe74a09a07db758f289e07ffa92d8b53 tagged as e.g. 6.1+3 and then we can use it.

Cheers
Christoph

> -----Original Message-----
> From: jdk-updates-dev <jdk-updates-dev-retn at openjdk.org> On Behalf Of
> Hohensee, Paul
> Sent: Freitag, 27. Januar 2023 21:23
> To: Bylokhov, Sergey <bylokhov at amazon.com>; jdk-updates-dev at openjdk.org
> Subject: Re: building the jtreg using jdk11.0.18
> 
> No objection from me! (
> 
> I've found another issue when backporting
> https://bugs.openjdk.org/browse/JDK-8299677, see the PRs
> 
> https://github.com/openjdk/jdk17u-dev/pull/1077
> https://github.com/openjdk/jdk11u-dev/pull/1667
> 
> These are failing pre-submit due to lack of jtreg/lib/junit-platform-console-
> standalone-1.8.2.jar in the github version jtreg, which defines the
> org/junit/jupiter package used by the new test
> test/jdk/java/util/Formatter/Padding.java. That jar file exists in the latest
> version of jtreg, so the test passes on my test host.
> 
> Thanks,
> Paul
> 
> On 1/26/23, 7:14 PM, "jdk-updates-dev on behalf of Sergey Bylokhov" <jdk-
> updates-dev-retn at openjdk.org on behalf of bylokhov at amazon.com> wrote:
> 
>     Hello,
> 
>     I would like to know what is our plan to fix all that issues occurred in our
> "github actions" for
>     jdk 11 and jdk 17. The root cause is an issue in the jtreg build script in the
> "branch-6.1+x"
>     branch, see:
>     https://github.com/openjdk/jtreg/pull/146
> 
>     So we can integrate that fix to the jtreg/"branch-6.1+x" and then use the
> next tag in our scripts.
>     Or we can just update the jtreg to to the latest one:branch-7.1+x
> 
>     Any objections to bump the version to 7.1.1+1 like the jdk/jdk did?
> 
>     --
>     Best regards, Sergey.