8291444: GHA builds/tests won't run manually if disabled from automatic running#11365
8291444: GHA builds/tests won't run manually if disabled from automatic running#11365RealCLanger wants to merge 3 commits intoopenjdk:masterfrom
Conversation
|
👋 Welcome back clanger! A progress list of the required criteria for merging this PR into |
|
@RealCLanger The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
|
@magicus @dholmes-ora FYA |
Webrevs
|
|
@RealCLanger This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been no new commits pushed to the ➡️ To integrate this PR with the above commit message to the |
|
Ping. Anybody from build group up to take a look? |
Yes, that sounds good. Please remove the commented lines. (I could have sworn I had already replied this, but either I forgot to press the green button, or I did it on the mobile and had connectivity issues I did not realize) |
|
Thanks for the reviews. I removed the commented lines. Will integrate later today. |
|
GHA error seems unrelated (langtools). |
|
Going to push as commit 5c0ff26.
Your commit was automatically rebased without conflicts. |
|
@RealCLanger Pushed as commit 5c0ff26. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
|
This change does not appear to have the fixed the issue it was filed to fix. The GHA tests still do not run for me when I choose a manual run. |
This is an attempt to fix the issue reported in JDK-8291444.
The check for secrets.JDK_SUBMIT_FILTER should only be applied to the push event but not on e.g. workflow_dispatch.
Currently setting JDK_SUBMIT_FILTER would lead to setting every platform to 'false', even when manually triggering the GHA run via workflow_dispatch.
I furthermore propose to relax the check for unknown events. In OpenJDK we only use/define workflow_dispatch and push. Other events would hence not trigger the workflow anyway. However, downstream vendors (like us in SapMachine) might use other events such as pull_request and they would then need to patch this away. This kind of downstream issue was also reported by Amazon. If you agree, I would remove the commented lines 91-93. Otherwise I have to uncomment them.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/11365/head:pull/11365$ git checkout pull/11365Update a local copy of the PR:
$ git checkout pull/11365$ git pull https://git.openjdk.org/jdk pull/11365/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 11365View PR using the GUI difftool:
$ git pr show -t 11365Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/11365.diff