-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
master
There have been numerous problems with the logic for removing bundles:
https://bugs.openjdk.org/browse/JDK-8340418
https://bugs.openjdk.org/browse/JDK-8336928
https://bugs.openjdk.org/browse/JDK-8338402
These problems can be avoided by relying on the built-in GHA mechanism for specifying a retention limit for these bundles[1]. In fact, a retention limit of 1 day is already specified[2].
An additional benefit to preserving the artifacts longer is that it increases the window for being able to download them for extra testing under different configurations than those tested by GHA (e.g. same test, different GC flags).
[1] https://docs.github.com/en/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization
[2] https://github.com/openjdk/jdk/blob/a45abf131be9ee52828c5db18a18847c45ae6994/.github/actions/upload-bundles/action.yml#L80C9-L80C23
https://bugs.openjdk.org/browse/JDK-8340418
https://bugs.openjdk.org/browse/JDK-8336928
https://bugs.openjdk.org/browse/JDK-8338402
These problems can be avoided by relying on the built-in GHA mechanism for specifying a retention limit for these bundles[1]. In fact, a retention limit of 1 day is already specified[2].
An additional benefit to preserving the artifacts longer is that it increases the window for being able to download them for extra testing under different configurations than those tested by GHA (e.g. same test, different GC flags).
[1] https://docs.github.com/en/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization
[2] https://github.com/openjdk/jdk/blob/a45abf131be9ee52828c5db18a18847c45ae6994/.github/actions/upload-bundles/action.yml#L80C9-L80C23
- relates to
-
JDK-8336928 GHA: Bundle artifacts removal broken
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk/29ae2651
-
Review(master)
openjdk/jdk/21801