Running JDK pre-submit testing on GitHub

Robin Westberg robin.westberg at
Thu Sep 24 04:19:06 UTC 2020

Hi Jaikiran,

> On 23 Sep 2020, at 18:20, Jaikiran Pai <jai.forums2013 at> wrote:
> Hello Robin,
> On 16/09/20 6:35 pm, Robin Westberg wrote:
>> If you would like to try this out yourself, simply add the file;!!GqivPVa7Brio!JLU3qSJBqEB5QdWCheIdBYdF4rwkFcl_r4MQSTaEJp9lV4dWOkAyJkzDEIRyP31PuZc$  with the same name and path to any branch in a local repository and push it to your personal fork. Within a few seconds, a new job should appear in the Actions tab in the GitHub web UI for your personal fork where you can view the progress.
> I decided to give this a try today for one of the patches I
> submitted[1]. I added this submit.yml to a duplicate branch (so as to
> avoid having it show up as a change/addition in the PR). The job did get
> triggered but ended up failing while trying to checkout jtreg[2]. It's a
> bit too late here, so I haven't yet investigated in more detail and
> instead decided to check here if there are any known issues in that
> workflow file.

Thanks for giving it a try! In the latest version of the submit.yml changes, there’s an additional file “make/conf/test-dependencies” [1] that you’ll need to add. Among other things it contains information of which version of jtreg to checkout (to avoid having to change the workflow file itself when JDK test dependencies change) so that should explain your failure (can be seen at [2]). So if you have time, please add this additional file as well to your duplicate branch and see if it works better!

Best regards,


> [1]*issuecomment-697518606__;Iw!!GqivPVa7Brio!JLU3qSJBqEB5QdWCheIdBYdF4rwkFcl_r4MQSTaEJp9lV4dWOkAyJkzDEIRy3odVX4M$ 
> [2];!!GqivPVa7Brio!JLU3qSJBqEB5QdWCheIdBYdF4rwkFcl_r4MQSTaEJp9lV4dWOkAyJkzDEIRyWY-hHrk$ 
> -Jaikiran

More information about the jdk-dev mailing list