-
Bug
-
Resolution: Fixed
-
P4
-
20
-
b03
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8291259 | 19.0.2 | Christoph Langer | P4 | Resolved | Fixed | b01 |
JDK-8290409 | 19.0.1 | Christoph Langer | P4 | Resolved | Fixed | b04 |
JDK-8290457 | 17.0.5 | Christoph Langer | P4 | Resolved | Fixed | b01 |
JDK-8299017 | 11.0.19 | Dukebot | P4 | Resolved | Fixed | b01 |
I think this is a good behavior, since it minimizes wait times for GHA results, and wastes less GHA resources.
I changed this to `false` while developing the new GHA framework, and intended to change it back before pushing, but forgot about it.
- backported by
-
JDK-8290409 Restore cancel-in-progress in GHA
-
- Resolved
-
-
JDK-8290457 Restore cancel-in-progress in GHA
-
- Resolved
-
-
JDK-8291259 Restore cancel-in-progress in GHA
-
- Resolved
-
-
JDK-8299017 Restore cancel-in-progress in GHA
-
- Resolved
-
- links to
-
Commit openjdk/jdk11u-dev/674218b0
-
Commit openjdk/jdk17u-dev/bebb6122
-
Commit openjdk/jdk19u/8ce19014
-
Commit openjdk/jdk/cb5ef3da
-
Review openjdk/jdk11u-dev/1554
-
Review openjdk/jdk17u-dev/557
-
Review openjdk/jdk19u/5
-
Review openjdk/jdk/9170