Run Weekly unittest retagger #14
graalvmbotci-unittest-retagger.yml
on: schedule
build-standalone-artifacts
/
generate-tier1
11s
build-standalone-artifacts
/
generate-tier2
12s
build-standalone-artifacts
/
generate-tier3
12s
Matrix: build-standalone-artifacts / tier1
Matrix: build-standalone-artifacts / tier2
Matrix: build-standalone-artifacts / tier3
Matrix: run-retagger
merge_all_reports
53s
Annotations
23 errors and 69 warnings
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
build-standalone-artifacts / tier2 (python-svm-build-gate-linux-amd64-jdk-latest, 7.78.6, 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.78.6, 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.78.6, 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.78.6, 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-batch10-linux-aarch64-jdk-latest, 7.78.6, 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-batch6-linux-amd64-jdk-latest, 7.78.6, 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.78.6, 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.78.6, 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.78.6, 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-batch9-linux-amd64-jdk-latest, 7.78.6, 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.78.6, 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-batch6-linux-aarch64-jdk-latest, 7.78.6, 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-batch4-linux-aarch64-jdk-latest, 7.78.6, 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-batch4-linux-amd64-jdk-latest, 7.78.6, 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.78.6, 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.78.6, 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.78.6, 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.78.6, 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.78.6, 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-batch7-linux-amd64-jdk-latest, 7.78.6, 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-batch12-linux-amd64-jdk-latest, 7.78.6, 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-batch13-linux-amd64-jdk-latest, 7.78.6, 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.78.6, 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.78.6, 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-batch14-linux-aarch64-jdk-latest, 7.78.6, 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-batch14-linux-amd64-jdk-latest, 7.78.6, 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-batch16-linux-amd64-jdk-latest, 7.78.6, 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-batch16-linux-aarch64-jdk-latest, 7.78.6, 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.78.6, 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-batch1-linux-amd64-jdk-latest, 7.78.6, 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.78.6, 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.78.6, 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.78.6, 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.78.6, 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.78.6, 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.78.6, 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-batch15-windows-amd64-jdk-latest, 7.78.6, 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.78.6, 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-batch10-windows-amd64-jdk-latest, 7.78.6, 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.78.6, 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-batch2-windows-amd64-jdk-latest, 7.78.6, 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.78.6, 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.78.6, 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.78.6, 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.78.6, 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.78.6, 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-batch8-windows-amd64-jdk-latest, 7.78.6, 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.78.6, 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.78.6, 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.78.6, 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-batch6-windows-amd64-jdk-latest, 7.78.6, 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.78.6, 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-batch16-windows-amd64-jdk-latest, 7.78.6, 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.78.6, 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-batch11-windows-amd64-jdk-latest, 7.78.6, 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.78.6, 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-batch13-windows-amd64-jdk-latest, 7.78.6, 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.78.6, 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.78.6, 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.78.6, 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-batch5-windows-amd64-jdk-latest, 7.78.6, 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.78.6, 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.78.6, 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.78.6, 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 windows-amd64 / tier1 (python-unittest-retagger-weekly-batch7-windows-amd64-jdk-latest, 7.78.6, 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.78.6, 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-batch15-linux-aarch64-jdk-latest, 7.78.6, 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-batch15-linux-amd64-jdk-latest, 7.78.6, 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
Expired
|
171 MB |
sha256:e97a753add95ef103e98041a04d78237945ed2bd2d38b835e76d203de7def7bd
|
|
|
graalpy-native-standalonelinux_aarch64
Expired
|
168 MB |
sha256:295dbe1b967e5c0f8db139b51eb21130702f3d81f384979a9ea4404b37084c37
|
|
|
graalpy-native-standalonewindows
Expired
|
107 MB |
sha256:23e7c99f23b86a38cc1366ddbb065b4fdc5518037d5cf103ce990c18ef956659
|
|
|
python-svm-build-gate-linux-aarch64-jdk-latest_logs
Expired
|
14.9 KB |
sha256:7918ce77d365d89be924c913b4a24f6054474356105bb840b1bc9bb8f899cc8e
|
|
|
python-svm-build-gate-linux-amd64-jdk-latest_logs
Expired
|
15.6 KB |
sha256:b722027f7c27971779432cc4670d8dbb5c9f930c9474bcf1c7423d84c4ba8575
|
|
|
python-svm-build-gate-windows-amd64-jdk-latest_logs
Expired
|
13.3 KB |
sha256:d5addedca612dcc689da710648c92540ea1133f02a50fbb81bcc5368f273d88b
|
|
|
python-unittest-retagger-weekly-batch1-linux-aarch64-jdk-latest_logs
Expired
|
37.6 KB |
sha256:212403f109815e3d0175844fd3ae6f333345637e94dd145438a6bdbce46445c0
|
|
|
python-unittest-retagger-weekly-batch1-linux-amd64-jdk-latest_logs
Expired
|
37.7 KB |
sha256:0790c550fec2106d6bcde8a41fa47f4f2cacd6c04e607a764da03e3ce3301dd4
|
|
|
python-unittest-retagger-weekly-batch1-windows-amd64-jdk-latest_logs
Expired
|
50.4 KB |
sha256:a7986b52f4487bda4571768606282b6f04c20344be3e3bec7955a7c2a64ef676
|
|
|
python-unittest-retagger-weekly-batch10-linux-aarch64-jdk-latest_logs
Expired
|
34.5 KB |
sha256:a171159eb34813811c079d51e6e03387555f1417ac7a403d0691f7f56431e081
|
|
|
python-unittest-retagger-weekly-batch10-linux-amd64-jdk-latest_logs
Expired
|
35.7 KB |
sha256:47c587bea33e70f07ec186e281b3cd90c1e2bda6b9a55b4e09d1505010879301
|
|
|
python-unittest-retagger-weekly-batch10-windows-amd64-jdk-latest_logs
Expired
|
44.7 KB |
sha256:0ac41b10561c548f3178db4367abdd150ad3e3ba3f35a72a8cfaa28c77dbc1ea
|
|
|
python-unittest-retagger-weekly-batch11-linux-aarch64-jdk-latest_logs
Expired
|
34 KB |
sha256:4c96001e7fb10d5a91e46042d21f9c4017a71e7cdc35ad3512e3ea910a1ea85d
|
|
|
python-unittest-retagger-weekly-batch11-linux-amd64-jdk-latest_logs
Expired
|
35 KB |
sha256:e3adb71fa7810df76bcc03cdbbe4609e120f7254128f7e646dcc15c0589af11b
|
|
|
python-unittest-retagger-weekly-batch11-windows-amd64-jdk-latest_logs
Expired
|
48.9 KB |
sha256:4462c18fbe4ea71c08b95057af27480a0690df56071bf4c23b631e5b6e39ea7f
|
|
|
python-unittest-retagger-weekly-batch12-linux-aarch64-jdk-latest_logs
Expired
|
27.3 KB |
sha256:83a59df67394998c223dc2aa21a600081b1b5793be8adc2d852728137ee5a2cf
|
|
|
python-unittest-retagger-weekly-batch12-linux-amd64-jdk-latest_logs
Expired
|
27.3 KB |
sha256:071159d276bea3d1a5ea2ed92ebc5719ffc9400cfef0c1c146afca28c2c17165
|
|
|
python-unittest-retagger-weekly-batch12-windows-amd64-jdk-latest_logs
Expired
|
41.8 KB |
sha256:254b45d171de7d84ede46fe3962c03732aa33010325206c109465da3c9c20104
|
|
|
python-unittest-retagger-weekly-batch13-linux-aarch64-jdk-latest_logs
Expired
|
35.2 KB |
sha256:9ebb70c14b2c78e7901e5e509201f098437c984468bff3199b77c6a2a40c2b48
|
|
|
python-unittest-retagger-weekly-batch13-linux-amd64-jdk-latest_logs
Expired
|
36.1 KB |
sha256:dad8b5864c15466877ea604ef5b0eb97c48283c44aba27b57c6d7977289453a4
|
|
|
python-unittest-retagger-weekly-batch13-windows-amd64-jdk-latest_logs
Expired
|
47.1 KB |
sha256:6e580b26dd23f888e851747b58391c94ee436c5a88a83964b271ed28dbd985be
|
|
|
python-unittest-retagger-weekly-batch14-linux-aarch64-jdk-latest_logs
Expired
|
14.1 KB |
sha256:f50e4b6eaf650b225eac6581aa94436bedc7a4413fc49efcd457afdcd8919ab5
|
|
|
python-unittest-retagger-weekly-batch14-linux-amd64-jdk-latest_logs
Expired
|
14.2 KB |
sha256:bbda413897e2eef4e917b87484c13871ac2fbffc8f5c11ebf426b154e4340c9a
|
|
|
python-unittest-retagger-weekly-batch14-windows-amd64-jdk-latest_logs
Expired
|
27.4 KB |
sha256:ed3a8ec9e184173c12f34ded7154ea9a6088cfcbd142468ffd42dcc08789e1e0
|
|
|
python-unittest-retagger-weekly-batch15-linux-aarch64-jdk-latest_logs
Expired
|
43.6 KB |
sha256:f0fc2897b57b7fe29aa6b61b23fc8c98296e61702b39c7b1aa63b223ca5333d2
|
|
|
python-unittest-retagger-weekly-batch15-linux-amd64-jdk-latest_logs
Expired
|
44.1 KB |
sha256:28e85967945c2c9913f32e9f0fb472cd939d602d64ac3b92b54766fc73f7b78a
|
|
|
python-unittest-retagger-weekly-batch15-windows-amd64-jdk-latest_logs
Expired
|
32.6 KB |
sha256:285426dc3675df9532290cc199e392ee9e3c398f46cf6bbce0ef7c266fa36222
|
|
|
python-unittest-retagger-weekly-batch16-linux-aarch64-jdk-latest_logs
Expired
|
42.2 KB |
sha256:c76fdad4a49b403995d5b1f1227186bb0c357c3f5d7f0c44c0c4c2a93d8a08c2
|
|
|
python-unittest-retagger-weekly-batch16-linux-amd64-jdk-latest_logs
Expired
|
43.3 KB |
sha256:cee754f906510106fd794531904ac9023800b9b7b198f4f9ce3ad64518419d57
|
|
|
python-unittest-retagger-weekly-batch16-windows-amd64-jdk-latest_logs
Expired
|
57.3 KB |
sha256:d46a4fdaa29026b515889631dc97646c111dea3af9846bffdecce7ee1edb93f5
|
|
|
python-unittest-retagger-weekly-batch2-linux-aarch64-jdk-latest_logs
Expired
|
16.1 KB |
sha256:2f5c80460b740a765dc77ad5cc698c250eba5054b2bfddb91a4d57b490eaf7b1
|
|
|
python-unittest-retagger-weekly-batch2-linux-amd64-jdk-latest_logs
Expired
|
16.4 KB |
sha256:cd3e52635beb29857bffbb46b2c9c1924ba00b241e7658d50d711a28202196db
|
|
|
python-unittest-retagger-weekly-batch2-windows-amd64-jdk-latest_logs
Expired
|
28.8 KB |
sha256:5db8c852fac3ba30e477ef9b06a2c9beb3469693be008146d9e5632585b81928
|
|
|
python-unittest-retagger-weekly-batch3-linux-aarch64-jdk-latest_logs
Expired
|
31.5 KB |
sha256:e6d64432cd4c9a7bb41cc569e74fbf45ab81575634b78d185850afe9a579b151
|
|
|
python-unittest-retagger-weekly-batch3-linux-amd64-jdk-latest_logs
Expired
|
32.6 KB |
sha256:f7b44ea62985bb446a8102485538404e6ce32d914e134815a26fba84ed1fd879
|
|
|
python-unittest-retagger-weekly-batch3-windows-amd64-jdk-latest_logs
Expired
|
13.2 KB |
sha256:e4aaa73ba6ba605d06a1827e1b690efea287f494b13f33d6a7c7181db3752a2a
|
|
|
python-unittest-retagger-weekly-batch4-linux-aarch64-jdk-latest_logs
Expired
|
39.3 KB |
sha256:9864f70d26ab4f614cd16a2fd6589f83245a73574649597645f965567cf24ef5
|
|
|
python-unittest-retagger-weekly-batch4-linux-amd64-jdk-latest_logs
Expired
|
40 KB |
sha256:2074f675b7b11ad3adbf2f20ebe6fd8941b5dc07c803c2fe3ad23d6a4f9834ba
|
|
|
python-unittest-retagger-weekly-batch4-windows-amd64-jdk-latest_logs
Expired
|
37.8 KB |
sha256:ebe989e32b65684bd2ab458b04b705daf156a19f62f922444f974b12fb96594b
|
|
|
python-unittest-retagger-weekly-batch5-linux-aarch64-jdk-latest_logs
Expired
|
29.5 KB |
sha256:979b4e8d4bbcd6ce821a7ac0105e1ef526ece0b1a56030c486ee8421ac868fef
|
|
|
python-unittest-retagger-weekly-batch5-linux-amd64-jdk-latest_logs
Expired
|
30.2 KB |
sha256:7b3146d9118da14d67a765a8760ae34a7ff217567308a9df5127e8c04d18d5bb
|
|
|
python-unittest-retagger-weekly-batch5-windows-amd64-jdk-latest_logs
Expired
|
43.4 KB |
sha256:7d8254badacb2c8f4393abff911fdf6bb746d69bbc00cb3584d5c21f6dc36268
|
|
|
python-unittest-retagger-weekly-batch6-linux-aarch64-jdk-latest_logs
Expired
|
18.3 KB |
sha256:437d3923d000adacd0391c6e3bcf3f9b21df4b671ca74668e6ef8c4f68a03491
|
|
|
python-unittest-retagger-weekly-batch6-linux-amd64-jdk-latest_logs
Expired
|
18.7 KB |
sha256:d924b513d93c85b24eae17257e3c97fb209495620fcf64497870db6b71f34ed5
|
|
|
python-unittest-retagger-weekly-batch6-windows-amd64-jdk-latest_logs
Expired
|
30.2 KB |
sha256:a8ed6a62ed802fedf6dcf53ddcc2e144394aa15f86921ab93864a8f9e61e7f8b
|
|
|
python-unittest-retagger-weekly-batch7-linux-aarch64-jdk-latest_logs
Expired
|
37.6 KB |
sha256:b5a8be6dd031e4fa66403fdbf807b9b7668796b5b276a8bf2ead28be85f248ee
|
|
|
python-unittest-retagger-weekly-batch7-linux-amd64-jdk-latest_logs
Expired
|
39.3 KB |
sha256:30d23eeab21ac21db596fc41d916696e5e40cb7c28120eec3d223204b3c10b9d
|
|
|
python-unittest-retagger-weekly-batch7-windows-amd64-jdk-latest_logs
Expired
|
48.6 KB |
sha256:7d25865f15a8e57321f547c051c318444df527647acfabae4268a38da29df8e2
|
|
|
python-unittest-retagger-weekly-batch8-linux-aarch64-jdk-latest_logs
Expired
|
49.1 KB |
sha256:0fb5fdd64cc822a5e4d26255f126bfd50ddd2fd612f07bd1611a713107f54cf3
|
|
|
python-unittest-retagger-weekly-batch8-linux-amd64-jdk-latest_logs
Expired
|
49.9 KB |
sha256:a54a87221d5c7380e57aad79763b4d37d20738b0e225aa6fceb65344d0dd9230
|
|
|
python-unittest-retagger-weekly-batch8-windows-amd64-jdk-latest_logs
Expired
|
41.3 KB |
sha256:a77d1b6da4877390388e44f9c3698d3cbc3ae49526373bb14d10e3bd94e3cb77
|
|
|
python-unittest-retagger-weekly-batch9-linux-aarch64-jdk-latest_logs
Expired
|
18.1 KB |
sha256:3959a536bf6590e5b3763a195fca23239bafb3dc6c9314bd4a7fa0021f2bbc39
|
|
|
python-unittest-retagger-weekly-batch9-linux-amd64-jdk-latest_logs
Expired
|
18.3 KB |
sha256:0d8f025c2b98b2fc8a4eadcdcab270e469ee30ad92a3b7473bc9340464ac1e5c
|
|
|
python-unittest-retagger-weekly-batch9-windows-amd64-jdk-latest_logs
Expired
|
31.5 KB |
sha256:7d8e18d5bcdb7b0f0d7f7ddb2a674fa346a59fef2874a55e115238b7b492e81a
|
|