Run Weekly unittest retagger #11
graalvmbotci-unittest-retagger.yml
on: schedule
build-standalone-artifacts
/
generate-tier1
12s
build-standalone-artifacts
/
generate-tier2
9s
build-standalone-artifacts
/
generate-tier3
11s
Matrix: build-standalone-artifacts / tier1
Matrix: build-standalone-artifacts / tier2
Matrix: build-standalone-artifacts / tier3
Matrix: run-retagger
merge_all_reports
48s
Annotations
24 errors and 68 warnings
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Run retagger on linux-aarch64 / tier1 (python-unittest-retagger-weekly-batch15-linux-aarch64-jdk-latest, 7.75.0, ubuntu-24.04-arm...
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
build-standalone-artifacts / tier2 (python-svm-build-gate-linux-amd64-jdk-latest, 7.75.0, ubuntu-latest, 1, 3.12.8, mx sforcei...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. 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/
|
|
build-standalone-artifacts / tier3 (python-svm-build-gate-linux-aarch64-jdk-latest, 7.75.0, ubuntu-24.04-arm, 1, 3.12.8, mx sf...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. 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/
|
|
build-standalone-artifacts / tier3 (python-svm-build-gate-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1, 3.8.10, mx sfor...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, microsoft/setup-msbuild@v1.0.2. 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/
|
|
build-standalone-artifacts / tier3 (python-svm-build-gate-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1, 3.8.10, mx sfor...
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/
|
|
Run retagger on linux-aarch64 / tier1 (python-unittest-retagger-weekly-batch6-linux-aarch64-jdk-latest, 7.75.0, ubuntu-24.04-arm,...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-aarch64 / tier1 (python-unittest-retagger-weekly-batch10-linux-aarch64-jdk-latest, 7.75.0, ubuntu-24.04-arm...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-amd64 / tier1 (python-unittest-retagger-weekly-batch9-linux-amd64-jdk-latest, 7.75.0, ubuntu-latest, 1, 3...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-amd64 / tier1 (python-unittest-retagger-weekly-batch10-linux-amd64-jdk-latest, 7.75.0, ubuntu-latest, 1, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-amd64 / tier1 (python-unittest-retagger-weekly-batch6-linux-amd64-jdk-latest, 7.75.0, ubuntu-latest, 1, 3...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-aarch64 / tier1 (python-unittest-retagger-weekly-batch9-linux-aarch64-jdk-latest, 7.75.0, ubuntu-24.04-arm,...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-aarch64 / tier1 (python-unittest-retagger-weekly-batch8-linux-aarch64-jdk-latest, 7.75.0, ubuntu-24.04-arm,...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-amd64 / tier1 (python-unittest-retagger-weekly-batch8-linux-amd64-jdk-latest, 7.75.0, ubuntu-latest, 1, 3...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-aarch64 / tier1 (python-unittest-retagger-weekly-batch4-linux-aarch64-jdk-latest, 7.75.0, ubuntu-24.04-arm,...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-amd64 / tier1 (python-unittest-retagger-weekly-batch2-linux-amd64-jdk-latest, 7.75.0, ubuntu-latest, 1, 3...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-amd64 / tier1 (python-unittest-retagger-weekly-batch4-linux-amd64-jdk-latest, 7.75.0, ubuntu-latest, 1, 3...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-aarch64 / tier1 (python-unittest-retagger-weekly-batch5-linux-aarch64-jdk-latest, 7.75.0, ubuntu-24.04-arm,...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-amd64 / tier1 (python-unittest-retagger-weekly-batch5-linux-amd64-jdk-latest, 7.75.0, ubuntu-latest, 1, 3...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-aarch64 / tier1 (python-unittest-retagger-weekly-batch2-linux-aarch64-jdk-latest, 7.75.0, ubuntu-24.04-arm,...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-aarch64 / tier1 (python-unittest-retagger-weekly-batch7-linux-aarch64-jdk-latest, 7.75.0, ubuntu-24.04-arm,...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-aarch64 / tier1 (python-unittest-retagger-weekly-batch13-linux-aarch64-jdk-latest, 7.75.0, ubuntu-24.04-arm...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-amd64 / tier1 (python-unittest-retagger-weekly-batch13-linux-amd64-jdk-latest, 7.75.0, ubuntu-latest, 1, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-amd64 / tier1 (python-unittest-retagger-weekly-batch12-linux-amd64-jdk-latest, 7.75.0, ubuntu-latest, 1, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-aarch64 / tier1 (python-unittest-retagger-weekly-batch12-linux-aarch64-jdk-latest, 7.75.0, ubuntu-24.04-arm...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-amd64 / tier1 (python-unittest-retagger-weekly-batch7-linux-amd64-jdk-latest, 7.75.0, ubuntu-latest, 1, 3...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-amd64 / tier1 (python-unittest-retagger-weekly-batch14-linux-amd64-jdk-latest, 7.75.0, ubuntu-latest, 1, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-aarch64 / tier1 (python-unittest-retagger-weekly-batch14-linux-aarch64-jdk-latest, 7.75.0, ubuntu-24.04-arm...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-aarch64 / tier1 (python-unittest-retagger-weekly-batch1-linux-aarch64-jdk-latest, 7.75.0, ubuntu-24.04-arm,...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-aarch64 / tier1 (python-unittest-retagger-weekly-batch16-linux-aarch64-jdk-latest, 7.75.0, ubuntu-24.04-arm...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-amd64 / tier1 (python-unittest-retagger-weekly-batch16-linux-amd64-jdk-latest, 7.75.0, ubuntu-latest, 1, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-amd64 / tier1 (python-unittest-retagger-weekly-batch1-linux-amd64-jdk-latest, 7.75.0, ubuntu-latest, 1, 3...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-aarch64 / tier1 (python-unittest-retagger-weekly-batch11-linux-aarch64-jdk-latest, 7.75.0, ubuntu-24.04-arm...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-amd64 / tier1 (python-unittest-retagger-weekly-batch11-linux-amd64-jdk-latest, 7.75.0, ubuntu-latest, 1, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch9-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5, microsoft/setup-msbuild@v1.0.2. 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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch9-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1...
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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch3-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5, microsoft/setup-msbuild@v1.0.2. 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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch3-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1...
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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch10-windows-amd64-jdk-latest, 7.75.0, windows-latest, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5, microsoft/setup-msbuild@v1.0.2. 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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch10-windows-amd64-jdk-latest, 7.75.0, windows-latest, ...
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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch15-windows-amd64-jdk-latest, 7.75.0, windows-latest, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5, microsoft/setup-msbuild@v1.0.2. 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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch15-windows-amd64-jdk-latest, 7.75.0, windows-latest, ...
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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch7-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5, microsoft/setup-msbuild@v1.0.2. 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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch7-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1...
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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch12-windows-amd64-jdk-latest, 7.75.0, windows-latest, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5, microsoft/setup-msbuild@v1.0.2. 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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch12-windows-amd64-jdk-latest, 7.75.0, windows-latest, ...
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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch1-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5, microsoft/setup-msbuild@v1.0.2. 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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch1-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1...
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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch2-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5, microsoft/setup-msbuild@v1.0.2. 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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch2-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1...
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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch14-windows-amd64-jdk-latest, 7.75.0, windows-latest, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5, microsoft/setup-msbuild@v1.0.2. 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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch14-windows-amd64-jdk-latest, 7.75.0, windows-latest, ...
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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch8-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5, microsoft/setup-msbuild@v1.0.2. 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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch8-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1...
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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch6-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5, microsoft/setup-msbuild@v1.0.2. 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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch6-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1...
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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch11-windows-amd64-jdk-latest, 7.75.0, windows-latest, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5, microsoft/setup-msbuild@v1.0.2. 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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch11-windows-amd64-jdk-latest, 7.75.0, windows-latest, ...
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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch16-windows-amd64-jdk-latest, 7.75.0, windows-latest, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5, microsoft/setup-msbuild@v1.0.2. 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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch16-windows-amd64-jdk-latest, 7.75.0, windows-latest, ...
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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch4-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5, microsoft/setup-msbuild@v1.0.2. 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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch4-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1...
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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch13-windows-amd64-jdk-latest, 7.75.0, windows-latest, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5, microsoft/setup-msbuild@v1.0.2. 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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch13-windows-amd64-jdk-latest, 7.75.0, windows-latest, ...
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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch5-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5, microsoft/setup-msbuild@v1.0.2. 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/
|
|
Run retagger on windows-amd64 / tier1 (python-unittest-retagger-weekly-batch5-windows-amd64-jdk-latest, 7.75.0, windows-latest, 1...
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/
|
|
Run retagger on linux-aarch64 / tier1 (python-unittest-retagger-weekly-batch3-linux-aarch64-jdk-latest, 7.75.0, ubuntu-24.04-arm,...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-amd64 / tier1 (python-unittest-retagger-weekly-batch3-linux-amd64-jdk-latest, 7.75.0, ubuntu-latest, 1, 3...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
Run retagger on linux-amd64 / tier1 (python-unittest-retagger-weekly-batch15-linux-amd64-jdk-latest, 7.75.0, ubuntu-latest, 1, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v5. 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/
|
|
merge_all_reports
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. 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 | |
|---|---|---|---|
|
graalpy-native-standalonelinux
|
173 MB |
sha256:e7877b60d5de315bd458400e009991241c72f78aa5722cd27cde16914700b50e
|
|
|
graalpy-native-standalonelinux_aarch64
|
169 MB |
sha256:9da8af657bd27c307b22702a5d8e3fa35d76494834edac3c3e186b1e5e695c3f
|
|
|
graalpy-native-standalonewindows
|
107 MB |
sha256:86eff0efe98d3768305792df2c3db04a0355efdadacf69972212a44a49b3bc81
|
|
|
python-unittest-retagger-weekly-batch1-linux-aarch64-jdk-latest_logs
|
37.5 KB |
sha256:42e149ba663be4e23774164b9a94a83cdfbe650e8e41d9f2a477a306f4c7e9e0
|
|
|
python-unittest-retagger-weekly-batch1-linux-amd64-jdk-latest_logs
|
38.2 KB |
sha256:1a38b5353491e35ec38dae2bec6f9fd7aeccbfc76ca54a4cfae600ceca74991f
|
|
|
python-unittest-retagger-weekly-batch1-windows-amd64-jdk-latest_logs
|
37.7 KB |
sha256:cce04224c82efbc71cd35d68f761647e2076b50cc4351d5fee6dc5d4154fa83d
|
|
|
python-unittest-retagger-weekly-batch10-linux-aarch64-jdk-latest_logs
|
34.4 KB |
sha256:ce9e87cb18392eeb70438977a514df2215d289603219f2c093fe6f1e9f306ba3
|
|
|
python-unittest-retagger-weekly-batch10-linux-amd64-jdk-latest_logs
|
35.7 KB |
sha256:9bc2444a74e932681dbb5a6c85cc86639b0d764dd9f94f11657c08f1e69d4ded
|
|
|
python-unittest-retagger-weekly-batch10-windows-amd64-jdk-latest_logs
|
31.8 KB |
sha256:c935148aff4b5e5a783a205e055c434cd6858d0a242c9358442b40385f40e5f0
|
|
|
python-unittest-retagger-weekly-batch11-linux-aarch64-jdk-latest_logs
|
34.2 KB |
sha256:7c10b8ebffd84ba8ba201cad15e056f77a44c1e7b0fde040ecadd3270d1a0c63
|
|
|
python-unittest-retagger-weekly-batch11-linux-amd64-jdk-latest_logs
|
34.7 KB |
sha256:b3c5ba68894585031cbedbf12036edbe4580b11242d334847a2f32ab481f3a1c
|
|
|
python-unittest-retagger-weekly-batch11-windows-amd64-jdk-latest_logs
|
35.9 KB |
sha256:eac870fee9276919d0489ae00b75c66e4f396eee865e1fc327a8460f50129c6e
|
|
|
python-unittest-retagger-weekly-batch12-linux-aarch64-jdk-latest_logs
|
27.8 KB |
sha256:64d8e9e000c2f1f5553964f1f10c7c07655aec18683f155a62d4cc3142d3d39e
|
|
|
python-unittest-retagger-weekly-batch12-linux-amd64-jdk-latest_logs
|
28.2 KB |
sha256:f214f1591ede89bc33883729b07bd5adbafc62ddf72a3ad3a57119fc955ad93f
|
|
|
python-unittest-retagger-weekly-batch12-windows-amd64-jdk-latest_logs
|
28.5 KB |
sha256:215655e9d4b1722c798a67c81fbf0876dc6bcf4e38a8c9ffc2c74a70a065f2d9
|
|
|
python-unittest-retagger-weekly-batch13-linux-aarch64-jdk-latest_logs
|
35.4 KB |
sha256:67bdfcb5d4d525d51b458a849564473d0e4dcc0d44b307effa64202c8fad04a2
|
|
|
python-unittest-retagger-weekly-batch13-linux-amd64-jdk-latest_logs
|
35.6 KB |
sha256:2c4955d6337c0adeac4a40ab74832b724adcf582465af2171756bcedfc4a664a
|
|
|
python-unittest-retagger-weekly-batch13-windows-amd64-jdk-latest_logs
|
34.1 KB |
sha256:80b24e1dec038dd0ce8821cee80c2a26ce98a71532d29910c278fefe34940374
|
|
|
python-unittest-retagger-weekly-batch14-linux-aarch64-jdk-latest_logs
|
14.1 KB |
sha256:4e15ee9142b3b41702874f15d1aa83fd0b59ada882e5f0304335369d44d99829
|
|
|
python-unittest-retagger-weekly-batch14-linux-amd64-jdk-latest_logs
|
14.4 KB |
sha256:2ec5ce4c3d7e359f760d7b70872f342ea87880ceec5d41282eb2cb5795285ef2
|
|
|
python-unittest-retagger-weekly-batch14-windows-amd64-jdk-latest_logs
|
14.1 KB |
sha256:bb4b643f2c273fa886902ad597c583e285df33c844e6d950be6515ab575bf0eb
|
|
|
python-unittest-retagger-weekly-batch15-linux-amd64-jdk-latest_logs
|
44.3 KB |
sha256:71d0d0cabf5ebddcc0f0a62ee86444506a0659f618d05782095c936cb730e516
|
|
|
python-unittest-retagger-weekly-batch15-windows-amd64-jdk-latest_logs
|
19.3 KB |
sha256:7b3c07686cda685e2be006f4b57a1ffdc2158374db7ce083d6e1bf2ac2098f8e
|
|
|
python-unittest-retagger-weekly-batch16-linux-aarch64-jdk-latest_logs
|
41.6 KB |
sha256:321c209b696e1671c819036cf8b4df984d9e9da23576913aa724b240582752ed
|
|
|
python-unittest-retagger-weekly-batch16-linux-amd64-jdk-latest_logs
|
42.9 KB |
sha256:7a47741741c187e550753f4e8de1fb551461853f1dce3bc4f611a6ebebfde30c
|
|
|
python-unittest-retagger-weekly-batch16-windows-amd64-jdk-latest_logs
|
44.2 KB |
sha256:95fa2a2346d529392ccbde8b2884f6b3af01b2990ca3e1898d66f37496f7342c
|
|
|
python-unittest-retagger-weekly-batch2-linux-aarch64-jdk-latest_logs
|
16.1 KB |
sha256:888e23f40edf01d4da4f32d6a4e99dc30cedd1bbca410e3bb2e00d9cd1e1bfc6
|
|
|
python-unittest-retagger-weekly-batch2-linux-amd64-jdk-latest_logs
|
16.3 KB |
sha256:d02fc5d8bd497c7723ea86ab42212831fb23a6d86c07968c218f1a289e252116
|
|
|
python-unittest-retagger-weekly-batch2-windows-amd64-jdk-latest_logs
|
15.8 KB |
sha256:35a3aa426a7b9728b64838f28786d15cac352fece64188faf4e67b3dcb45a69e
|
|
|
python-unittest-retagger-weekly-batch3-linux-aarch64-jdk-latest_logs
|
31.4 KB |
sha256:791ef6c2587e544d85097978bac1d1be77c518617670427697c4ae663d47027a
|
|
|
python-unittest-retagger-weekly-batch3-linux-amd64-jdk-latest_logs
|
33.9 KB |
sha256:9c57de498094b86d69ecac0127c8c6f01759897cd2f79d236caab3842e30da69
|
|
|
python-unittest-retagger-weekly-batch4-linux-aarch64-jdk-latest_logs
|
39.3 KB |
sha256:f986ac875f21ee38ae0954bb7ebbf426594724df70bafb03787510f46927f571
|
|
|
python-unittest-retagger-weekly-batch4-linux-amd64-jdk-latest_logs
|
40.3 KB |
sha256:89b79f5d0533a1e370e58ceeff242e6de62cbe0c90c620a9e743edb36e3db1e9
|
|
|
python-unittest-retagger-weekly-batch4-windows-amd64-jdk-latest_logs
|
24.8 KB |
sha256:71d9da63d6fc093e7fdbc559747292aca7f32ef4e18364bd56b440f96e81a9f7
|
|
|
python-unittest-retagger-weekly-batch5-linux-aarch64-jdk-latest_logs
|
29.5 KB |
sha256:e8c2c8f0d8f371b1e7902e1dc27907a8eb20a672da54836178e3c1a1b07c9919
|
|
|
python-unittest-retagger-weekly-batch5-linux-amd64-jdk-latest_logs
|
30.1 KB |
sha256:2a3b7728821610e8ed5c28135ec098081400b7dddb858bf521b4ba0b9eae4aae
|
|
|
python-unittest-retagger-weekly-batch5-windows-amd64-jdk-latest_logs
|
30.1 KB |
sha256:9262d6738fe623ec92629702f17179def2f5c24fa9c27e722f81ac5e5ef4068c
|
|
|
python-unittest-retagger-weekly-batch6-linux-aarch64-jdk-latest_logs
|
18.3 KB |
sha256:445a95d9c35d19de548bdbf13a741b047c05f7db017789f656c2f379678297be
|
|
|
python-unittest-retagger-weekly-batch6-linux-amd64-jdk-latest_logs
|
18.8 KB |
sha256:187c18696c36fc89f044c0e25c5d105f9c50ed0b9c7bf89294756299c990df97
|
|
|
python-unittest-retagger-weekly-batch6-windows-amd64-jdk-latest_logs
|
17.2 KB |
sha256:1f0c8292f3158e69cccb48de44c0b7e3c147caff38d75f509163de52887e67dd
|
|
|
python-unittest-retagger-weekly-batch7-linux-aarch64-jdk-latest_logs
|
37.5 KB |
sha256:43193decb094fc99ebf4ccb52a37eb33b3930f80083d41ab63b1bb2991c820ea
|
|
|
python-unittest-retagger-weekly-batch7-linux-amd64-jdk-latest_logs
|
38.7 KB |
sha256:f0f5688cb5963d63aae012c7a336496c6c2a42b7bf68ebe4885aba59d269c9bf
|
|
|
python-unittest-retagger-weekly-batch8-linux-aarch64-jdk-latest_logs
|
48.6 KB |
sha256:1eee5b1cbe32149bbd5ac414b6d162740b23a9362a68644861c1a58ab3426631
|
|
|
python-unittest-retagger-weekly-batch8-linux-amd64-jdk-latest_logs
|
49.8 KB |
sha256:c80e5b2e8c97abfa893ae301644dbf8b58556578d7c0f57f77c940f1c4f7cfc3
|
|
|
python-unittest-retagger-weekly-batch8-windows-amd64-jdk-latest_logs
|
28 KB |
sha256:a90387cbef8dac8b611ea94fa810fe0d8e1f8c2257668218b0e0959bd35bf5f5
|
|
|
python-unittest-retagger-weekly-batch9-linux-aarch64-jdk-latest_logs
|
17.8 KB |
sha256:cd3345fa39786f2d6b799201e390c5bdad9db7bf4d8468d6b29d921c8b688b55
|
|
|
python-unittest-retagger-weekly-batch9-linux-amd64-jdk-latest_logs
|
18.3 KB |
sha256:31868b6fefc6807b74e99c1690a31e6803e4bed3ba765d4e1bb4a32c4991f7bb
|
|
|
python-unittest-retagger-weekly-batch9-windows-amd64-jdk-latest_logs
|
18.5 KB |
sha256:de8262897db5597680ea4e437ead380f4b828dca4e699baf9feab1ba82a9be4a
|
|