Merge tag 'jdk-11.0.31+11' into dragonwell_extended-11.0.31.28.11 #554
main.yml
on: pull_request
Prerequisites
/
Check Commit Message
47s
Prerequisites
/
Prerequisites
46s
Matrix: linux-aarch64 / build
Matrix: linux-x64 / build
Matrix: windows-x64 / build
Matrix: riscv64 / build
Matrix: linux-aarch64 / test
Matrix: linux-x64 / test
Matrix: windows-x64 / test
Waiting for pending jobs
Annotations
2 errors and 26 warnings
|
windows-x64 / build (release)
Build failed. See summary for details.
|
|
windows-x64 / build (debug)
Build failed. See summary for details.
|
|
Prerequisites / Prerequisites
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Prerequisites / Prerequisites
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Prerequisites / Prerequisites
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Prerequisites / Prerequisites
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Prerequisites / Prerequisites
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Prerequisites / Prerequisites
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Prerequisites / Prerequisites
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Prerequisites / Prerequisites
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Prerequisites / Prerequisites
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Prerequisites / Check Commit Message
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2, dragonwell-releng/check_commit_action@master. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
riscv64 / build (release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-x64 / build (release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/cache@v4, actions/checkout@v4, actions/github-script@v7, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-x64 / build (debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/cache@v4, actions/checkout@v4, actions/github-script@v7, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-x64 / build (release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/cache@v4, actions/checkout@v3, actions/checkout@v4, actions/github-script@v6, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-x64 / build (debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/cache@v4, actions/checkout@v3, actions/checkout@v4, actions/github-script@v6, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-x64 / test (hs/tier1 serviceability)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-x64 / test (hs/tier1 runtime)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-x64 / test (jdk/tier1 part 1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-x64 / test (jdk/tier1 part 2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-x64 / test (dragonwell/jdk feature)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-x64 / test (hs/tier1 common)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-x64 / test (jdk/tier1 part 3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-x64 / test (dragonwell/hs feature)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-x64 / test (hs/tier1 compiler)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-x64 / test (hs/tier1 gc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-x64 / test (langtools/tier1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
bundles-linux-aarch64
Expired
|
795 MB |
sha256:6406d546b36a0fc96d53660cec9099c67b26565836b8351977e4716ab431e19c
|
|
|
bundles-linux-aarch64-debug
Expired
|
725 MB |
sha256:bf0828d335ff4ed25976d7326efa9875fc299e8d28b54b8e5b6a6e2f63352728
|
|
|
bundles-linux-x64
Expired
|
849 MB |
sha256:977d2849f54c87841f21913d59cbeb0aa33559aea4b4774fb4fbb79be985dc3a
|
|
|
bundles-linux-x64-debug
Expired
|
778 MB |
sha256:6c559d8b85fa45cd6824a1fb15b63c894101af1cdbffd8ab698a5847ba26bfff
|
|
|
failure-logs-windows-x64
Expired
|
28.7 KB |
sha256:3f6455ecb8ec7839f5c7d5bdd3e9dafe74ccb2298a0b1e5c8a7772c088963252
|
|
|
failure-logs-windows-x64-debug
Expired
|
28.7 KB |
sha256:bf5830843fbfe3cbd99835c14172334906c6426a8e82894e1c25450d4cbe2f6d
|
|
|
results-linux-aarch64-dragonwell_hs_feature
Expired
|
128 KB |
sha256:840a89dcaf53256f26176cda2245e4ca60a03b070837af490c54bc83ac96ed19
|
|
|
results-linux-aarch64-dragonwell_jdk_feature
Expired
|
488 KB |
sha256:1c1d77a55fe4fdcaa5af8f4b74ef752bb2435e195c9386880a99247a80bca989
|
|
|
results-linux-aarch64-hs_tier1_common
Expired
|
27.4 KB |
sha256:fdcc51c67a282ce6b1db791e2361e11d4423f2dc4795959a0aff7e2da168ce01
|
|
|
results-linux-aarch64-hs_tier1_compiler
Expired
|
2.25 MB |
sha256:7bdcb7b4b3e81adcd9b7dc7e2c0f263148847f14b58ef2d83f71b3b6fe30c27f
|
|
|
results-linux-aarch64-hs_tier1_gc
Expired
|
1.06 MB |
sha256:7908d8479c47d9d2250fb2423095d91cda84a5c71ce07dfe4ecfee01eb205769
|
|
|
results-linux-aarch64-hs_tier1_runtime
Expired
|
1.22 MB |
sha256:eea2cd662ebc6f061603e5c50fe03377eb1ffe3220571f01263b5c9ddd14d226
|
|
|
results-linux-aarch64-hs_tier1_serviceability
Expired
|
281 KB |
sha256:2b6c3db5fc7105c3275dcf0ae81ccb007add19bba0fad49a55a1affb9d8183dd
|
|
|
results-linux-aarch64-jdk_tier1_part_1
Expired
|
2.24 MB |
sha256:d8999c0b276943f350b2991615ed68acd94ed72897c3ca769ad5de650f7f796c
|
|
|
results-linux-aarch64-jdk_tier1_part_2
Expired
|
2.38 MB |
sha256:b0bb420f466011e7d60a5a8bf3d43d2cf98ca6d3165952e1f2094513d40e3856
|
|
|
results-linux-aarch64-jdk_tier1_part_3
Expired
|
595 KB |
sha256:7884301af31537f9146a42f103c6d3987a3fbe4ad97ffa60ad0c8e3e56878df1
|
|
|
results-linux-aarch64-langtools_tier1
Expired
|
8.52 MB |
sha256:ea835d9a50981442493b2c7cffe7920f7476e120224abf7ae6ad682f0b27942f
|
|
|
results-linux-x64-dragonwell_hs_feature
Expired
|
129 KB |
sha256:61433a3b06a77d75cdaef034bbeba713db57f7768977d925d6b4b8d7cdfba8eb
|
|
|
results-linux-x64-dragonwell_jdk_feature
Expired
|
479 KB |
sha256:3107b72fe34b1d8b95532fa0312ebef92800bb7534e0df3259ef1383913e908a
|
|
|
results-linux-x64-hs_tier1_common
Expired
|
26.8 KB |
sha256:079e7c1facdafa65cd975161117b1e2df673c4c9d0d5c9965360669980a46a7e
|
|
|
results-linux-x64-hs_tier1_compiler
Expired
|
2.05 MB |
sha256:a733bd5014345deb08726f753073d31008a61217211461f3907a17521bde8935
|
|
|
results-linux-x64-hs_tier1_gc
Expired
|
1.04 MB |
sha256:aa931b5df09351cb92c883ee01b2b9339e0e5a7e0730182dd866375c3ccc4c0f
|
|
|
results-linux-x64-hs_tier1_runtime
Expired
|
1.2 MB |
sha256:c2605f6931063b806266a31dee4391000eae486c3d24c87d97f77be1e38adc84
|
|
|
results-linux-x64-hs_tier1_serviceability
Expired
|
280 KB |
sha256:49b762288d90324d46a9ed91a9bf8f3ab765dff60168028ccd5d50841061cd32
|
|
|
results-linux-x64-jdk_tier1_part_1
Expired
|
2.2 MB |
sha256:61c167ac9d9ea9a78f4079fc5ccdc26063de95fcd048ec545f3f4877bfc078dd
|
|
|
results-linux-x64-jdk_tier1_part_2
Expired
|
2.34 MB |
sha256:683b49761125e734a70ae25de668bd09a49a83ca14d4f6b9a2fc1e5f366aec07
|
|
|
results-linux-x64-jdk_tier1_part_3
Expired
|
595 KB |
sha256:38864b157624657e0a8b80b8fccc2b48697ef8272f5e5e2f1043ffa797776e4c
|
|
|
results-linux-x64-langtools_tier1
Expired
|
8.43 MB |
sha256:a12ab5994fc484cb5f3bc52ae8b25852c8e59c1e618cf92802f65914d86b079a
|
|