Is jdk-submit no longer available for committers?

[Jaikiran Pai]

Hello Aleksey,

On 24/11/21 1:27 pm, Aleksey Shipilev wrote:
> Hi,
>
> On 11/24/21 6:48 AM, Jaikiran Pai wrote:
>> I have been trying to find a way to run tier2 tests before submitting a
>> change to the JDK project. I don't have the necessary infrastructure to
>> do it locally. 
>
> IIRC, jdk-submit did not ran tier2?

I'm not sure. I myself hadn't used it previously. The introduction 
mail[1] hadn't mentioned any specific tiers/tests so I always assumed 
that it would run all tests against all the tested platforms.

>
> In my experience, tier2 takes about the same time as tier1, so as long 
> as you have capacity to run tier1 (which is recommended for 
> non-trivial integrations anyway), you should be able to run tier2. A 
> decent desktop should complete it within a few hours.

You are right indeed. Before sending this mail, I had triggered a 
(subset) of tier2 (specifically jdk:tier2) on my local setup and that 
just completed a while back. So that indeed is good news for me for any 
future testing. My previous attempt at running tier2 around a year back 
wasn't so successful and I had to kill it after multiple hours of it 
continuing to run.

>> Is jdk-submit no longer functional? I can't find a git repo for it under
>> the openjdk repo at github.
>
> jdk-submit was replaced by GitHub Actions workflows.
>
For tier1 testing GitHub Actions has indeed been very helpful, 
especially the ability to trigger manual builds of specific branches 
against specific platforms of choice. I wonder if I can come up with a 
new GitHub workflow to trigger tier2 tests for all platforms against it 
- perhaps not for each PR but for manual/on-demand runs. I'll experiment 
a bit some time soon.

[1] https://mail.openjdk.java.net/pipermail/jdk-dev/2018-January/000566.html

-Jaikiran