Skip to content

[GR-61894] Eagerly initialize native thread state. #195

[GR-61894] Eagerly initialize native thread state.

[GR-61894] Eagerly initialize native thread state. #195

Triggered via pull request April 7, 2026 14:50
Status Failure
Total duration 7h 21m 27s
Artifacts 43

ci-unittests.yml

on: pull_request
build-standalone-artifacts  /  generate-tier1
12s
build-standalone-artifacts / generate-tier1
build-standalone-artifacts  /  generate-tier2
11s
build-standalone-artifacts / generate-tier2
build-standalone-artifacts  /  generate-tier3
13s
build-standalone-artifacts / generate-tier3
Matrix: build-standalone-artifacts / tier1
Matrix: build-standalone-artifacts / tier2
Matrix: build-standalone-artifacts / tier3
run-tests  /  generate-tier1
11s
run-tests / generate-tier1
run-tests  /  generate-tier2
13s
run-tests / generate-tier2
run-tests  /  generate-tier3
13s
run-tests / generate-tier3
Matrix: run-tests / tier1
Matrix: run-tests / tier2
Matrix: run-tests / tier3
collect-reports
11s
collect-reports
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 70 warnings
run-tests / tier3 (python-junit-gate-windows-amd64-jdk-latest, 7.78.1, windows-latest, 1, 3.8.10, mx sforceim...
The job has exceeded the maximum execution time of 6h0m0s
build-standalone-artifacts / tier1 (style-ecj-gate-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 0, 3.8.12, mx sforceimports ...
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 / tier1 (style-gate-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 0, 3.8.12, mx sforceimports mx -...
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 / tier2 (python-svm-build-gate-linux-amd64-jdk-latest, 7.78.1, 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.1, 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.1, 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.1, 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-tests / tier1 (tier1, ubuntu-latest, 1, 3.12.8, 'pylint==2.4' 'astroid==2.4', true, utf-8, true)
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/
run-tests / tier1 (tier1, ubuntu-latest, 1, 3.12.8, 'pylint==2.4' 'astroid==2.4', true, utf-8, true)
No files were found with the provided path: /tmp/test-report-*.json. No artifacts will be uploaded.
run-tests / tier2 (tier2, ubuntu-latest, 1, 3.12.8, 'pylint==2.4' 'astroid==2.4', true, utf-8, true)
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/
run-tests / tier2 (tier2, ubuntu-latest, 1, 3.12.8, 'pylint==2.4' 'astroid==2.4', true, utf-8, true)
No files were found with the provided path: /tmp/test-report-*.json. No artifacts will be uploaded.
run-tests / tier2 (python-unittest-jython-gate-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12.8, mx s...
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-tests / tier2 (python-tagged-unittest-gate-batch2-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12....
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-tests / tier2 (python-tagged-unittest-gate-batch6-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12....
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-tests / tier2 (python-tagged-unittest-gate-batch4-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12....
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-tests / tier2 (python-tagged-unittest-gate-batch1-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12....
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-tests / tier2 (python-tagged-unittest-gate-batch8-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12....
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-tests / tier2 (python-tagged-unittest-gate-batch5-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12....
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-tests / tier2 (python-unittest-arrow-storage-gate-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12....
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-tests / tier2 (python-unittest-gate-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12.8, mx sforceim...
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-tests / tier2 (python-tagged-unittest-gate-batch3-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12....
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-tests / tier2 (python-unittest-multi-context-gate-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12....
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-tests / tier2 (python-tagged-unittest-gate-batch7-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12....
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-tests / tier3 (tier3, ubuntu-latest, 1, 3.12.8, 'pylint==2.4' 'astroid==2.4', true, utf-8, true)
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/
run-tests / tier3 (tier3, ubuntu-latest, 1, 3.12.8, 'pylint==2.4' 'astroid==2.4', true, utf-8, true)
No files were found with the provided path: /tmp/test-report-*.json. No artifacts will be uploaded.
run-tests / tier3 (python-tagged-unittest-gate-batch2-linux-aarch64-jdk-latest, 7.78.1, ubuntu-24.04-arm, 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-tests / tier3 (python-tagged-unittest-gate-batch4-linux-aarch64-jdk-latest, 7.78.1, ubuntu-24.04-arm, 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-tests / tier3 (python-tagged-unittest-gate-batch1-linux-aarch64-jdk-latest, 7.78.1, ubuntu-24.04-arm, 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-tests / tier3 (python-unittest-hpy-gate-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12.8, mx sfor...
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-tests / tier3 (python-unittest-hpy-gate-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12.8, mx sfor...
No files were found with the provided path: /tmp/test-report-*.json. No artifacts will be uploaded.
run-tests / tier3 (python-tagged-unittest-gate-batch8-linux-aarch64-jdk-latest, 7.78.1, ubuntu-24.04-arm, 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-tests / tier3 (python-tagged-unittest-gate-batch5-linux-aarch64-jdk-latest, 7.78.1, ubuntu-24.04-arm, 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-tests / tier3 (python-tagged-unittest-gate-batch6-linux-aarch64-jdk-latest, 7.78.1, ubuntu-24.04-arm, 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-tests / tier3 (python-tagged-unittest-gate-batch7-linux-aarch64-jdk-latest, 7.78.1, ubuntu-24.04-arm, 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-tests / tier3 (python-tagged-unittest-gate-batch3-linux-aarch64-jdk-latest, 7.78.1, ubuntu-24.04-arm, 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-tests / tier3 (python-junit-gate-linux-aarch64-jdk-latest, 7.78.1, ubuntu-24.04-arm, 1, 3.12.8, mx sforce...
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-tests / tier3 (python-junit-gate-linux-aarch64-jdk-latest, 7.78.1, ubuntu-24.04-arm, 1, 3.12.8, mx sforce...
No files were found with the provided path: /tmp/test-report-*.json. No artifacts will be uploaded.
run-tests / tier3 (python-graalvm-gate-linux-aarch64-jdk-latest, 7.78.1, ubuntu-24.04-arm, 1, 3.12.8, mx sfor...
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-tests / tier3 (python-graalvm-gate-linux-aarch64-jdk-latest, 7.78.1, ubuntu-24.04-arm, 1, 3.12.8, mx sfor...
No files were found with the provided path: /tmp/test-report-*.json. No artifacts will be uploaded.
run-tests / tier3 (python-junit-manual-interpreter-gate-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.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-tests / tier3 (python-junit-manual-interpreter-gate-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.1...
No files were found with the provided path: /tmp/test-report-*.json. No artifacts will be uploaded.
run-tests / tier3 (python-junit-gate-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12.8, mx sforceimpor...
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-tests / tier3 (python-junit-gate-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12.8, mx sforceimpor...
No files were found with the provided path: /tmp/test-report-*.json. No artifacts will be uploaded.
run-tests / tier3 (python-junit-maven-gate-linux-aarch64-jdk-latest, 7.78.1, ubuntu-24.04-arm, 1, 3.12.8, mx ...
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/
run-tests / tier3 (python-junit-maven-gate-linux-aarch64-jdk-latest, 7.78.1, ubuntu-24.04-arm, 1, 3.12.8, mx ...
No files were found with the provided path: /tmp/test-report-*.json. No artifacts will be uploaded.
run-tests / tier3 (python-unittest-standalone-gate-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12.8, ...
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-tests / tier3 (python-unittest-standalone-gate-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12.8, ...
No files were found with the provided path: /tmp/test-report-*.json. No artifacts will be uploaded.
run-tests / tier3 (python-graalvm-gate-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12.8, mx sforceimp...
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-tests / tier3 (python-graalvm-gate-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12.8, mx sforceimp...
No files were found with the provided path: /tmp/test-report-*.json. No artifacts will be uploaded.
run-tests / tier3 (python-unittest-standalone-gate-linux-aarch64-jdk-latest, 7.78.1, ubuntu-24.04-arm, 1, 3.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-tests / tier3 (python-unittest-standalone-gate-linux-aarch64-jdk-latest, 7.78.1, ubuntu-24.04-arm, 1, 3.1...
No files were found with the provided path: /tmp/test-report-*.json. No artifacts will be uploaded.
run-tests / tier3 (python-junit-maven-gate-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12.8, mx sforc...
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/
run-tests / tier3 (python-junit-maven-gate-linux-amd64-jdk-latest, 7.78.1, ubuntu-latest, 1, 3.12.8, mx sforc...
No files were found with the provided path: /tmp/test-report-*.json. No artifacts will be uploaded.
run-tests / tier3 (python-graalvm-gate-windows-amd64-jdk-latest, 7.78.1, windows-latest, 1, 3.8.10, mx sforce...
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-tests / tier3 (python-graalvm-gate-windows-amd64-jdk-latest, 7.78.1, windows-latest, 1, 3.8.10, mx sforce...
No files were found with the provided path: /tmp/test-report-*.json. No artifacts will be uploaded.
run-tests / tier3 (python-graalvm-gate-windows-amd64-jdk-latest, 7.78.1, windows-latest, 1, 3.8.10, mx sforce...
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-tests / tier3 (python-unittest-standalone-gate-batch2-windows-amd64-jdk-latest, 7.78.1, 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-tests / tier3 (python-unittest-standalone-gate-batch2-windows-amd64-jdk-latest, 7.78.1, windows-latest, 1...
No files were found with the provided path: /tmp/test-report-*.json. No artifacts will be uploaded.
run-tests / tier3 (python-unittest-standalone-gate-batch2-windows-amd64-jdk-latest, 7.78.1, 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-tests / tier3 (python-unittest-gate-linux-aarch64-jdk-latest, 7.78.1, ubuntu-24.04-arm, 1, 3.12.8, mx sfo...
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/
run-tests / tier3 (python-unittest-standalone-gate-batch1-windows-amd64-jdk-latest, 7.78.1, 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-tests / tier3 (python-unittest-standalone-gate-batch1-windows-amd64-jdk-latest, 7.78.1, windows-latest, 1...
No files were found with the provided path: /tmp/test-report-*.json. No artifacts will be uploaded.
run-tests / tier3 (python-unittest-standalone-gate-batch1-windows-amd64-jdk-latest, 7.78.1, 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-tests / tier3 (python-junit-maven-gate-windows-amd64-jdk-latest, 7.78.1, windows-latest, 1, 3.8.10, 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, 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-tests / tier3 (python-junit-maven-gate-windows-amd64-jdk-latest, 7.78.1, windows-latest, 1, 3.8.10, mx sf...
No files were found with the provided path: /tmp/test-report-*.json. No artifacts will be uploaded.
run-tests / tier3 (python-junit-maven-gate-windows-amd64-jdk-latest, 7.78.1, windows-latest, 1, 3.8.10, mx sf...
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-tests / tier3 (python-unittest-native-debug-build-gate-linux-amd64-jdk-latest, 7.78.1, 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/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-tests / tier3 (python-unittest-gate-windows-amd64-jdk-latest, 7.78.1, windows-latest, 1, 3.8.10, mx sforc...
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/
run-tests / tier3 (python-unittest-gate-windows-amd64-jdk-latest, 7.78.1, windows-latest, 1, 3.8.10, mx sforc...
No files were found with the provided path: /tmp/test-report-*.json. No artifacts will be uploaded.
run-tests / tier3 (python-unittest-gate-windows-amd64-jdk-latest, 7.78.1, windows-latest, 1, 3.8.10, mx sforc...
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/
collect-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/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/

Artifacts

Produced during runtime
Name Size Digest
graal-jdk-latestlinux Expired
335 MB
sha256:c265ec52c57245f9902b3dcf873c3f602628450efa0629a4c82a4ea472d27bea
graal-jdk-latestlinux_aarch64 Expired
311 MB
sha256:5ad73c1d596d88d44dbfb25ffbb6f23d31b911f7a966e3ab4f0b1c81daaee9cd
graal-jdk-latestwindows Expired
327 MB
sha256:be053fca7e838ef64c1cbf5c1b7b9d3121ede0599ab5ed488038b95e98a5c05d
graalpy-jvm-standalonelinux Expired
143 MB
sha256:72e73c48fc38f42aa42bda4c34ff0d69d667a8a97ae46dc824260969559caca6
graalpy-native-standalonelinux Expired
172 MB
sha256:795c314b93f7b00e729c23e1639b696ad06b4bc44f6b6fc405a0501ff4593677
graalpy-native-standalonelinux_aarch64 Expired
169 MB
sha256:5cee10a783ffb45a49dc5c618780a59d56929ec030ac428fc3d1037514e490e4
graalpy-native-standalonewindows Expired
107 MB
sha256:7032cf9317264916403dbb0941b0927e00fa660ab8c0868c41c84b64f2dfa3a2
merged_test_reports
404 Bytes
sha256:e5123951294e56d0e580e1c1341b96fb156433bf704835fa22a1023e584a1940
python-graalvm-gate-linux-aarch64-jdk-latest_logs Expired
14.9 KB
sha256:189d6990635dba4de63330999b5081a3508be5fa707c4fd1778e678606840a56
python-graalvm-gate-linux-amd64-jdk-latest_logs Expired
15.5 KB
sha256:bc1c66ed1d97ca3b0d98ea8968bfaa449602182dc6e67d2a72011b8ac0718672
python-graalvm-gate-windows-amd64-jdk-latest_logs Expired
13.2 KB
sha256:c41e445f4ef5dc2e5e56ef753a42445dfc3d49976f9931d17df7b509bf340d54
python-junit-maven-gate-linux-aarch64-jdk-latest_logs Expired
59.1 KB
sha256:0f33203e668fb79540c0ca095ea113b28310189293f5cdb58143aef354d9c769
python-junit-maven-gate-linux-amd64-jdk-latest_logs Expired
61.7 KB
sha256:7003a673908fa16f2f45f5faacff7c353eb07218c9aedcedec4a49ac6fcf3065
python-junit-maven-gate-windows-amd64-jdk-latest_logs Expired
52.5 KB
sha256:ba866f1ff14753e6972f80d5aced02289a8239faa3ca1ab6644a348dc39af709
python-svm-build-gate-linux-aarch64-jdk-latest_logs Expired
14.9 KB
sha256:021cb8c0ed405e22c1b0903e38c174c9703f4835b519651da08f4c573ad169f2
python-svm-build-gate-linux-amd64-jdk-latest_logs Expired
15.5 KB
sha256:f8ef5cb7221c9fc93a0909a8eb407f5224be52f258ce019cec046cc2c2d91fc4
python-svm-build-gate-windows-amd64-jdk-latest_logs Expired
13.3 KB
sha256:b3ed09d2cd716bc062fc2c15ab120c11848707d78c52a5aceeba8467f1195419
python-tagged-unittest-gate-batch1-linux-aarch64-jdk-latest_test_reports Expired
47.4 KB
sha256:92738d2cd2998516e8794e9c79f45f64b03d4e3044f40545ab0b333daad9792e
python-tagged-unittest-gate-batch1-linux-amd64-jdk-latest_test_reports Expired
48 KB
sha256:72360cb2f675ebeadeb23752906de0c1222b7fd7e95a95e91db0f6874b6848bf
python-tagged-unittest-gate-batch2-linux-aarch64-jdk-latest_test_reports Expired
42.9 KB
sha256:4a277733d362a4567a73b710660d19cb00a5f6e16eeca5044689a0bf5025ae51
python-tagged-unittest-gate-batch2-linux-amd64-jdk-latest_test_reports Expired
43.7 KB
sha256:722663968c7124f61ab5fdbc81923fb0e13e1bd32e49103fd8647ef33e3d79c9
python-tagged-unittest-gate-batch3-linux-aarch64-jdk-latest_test_reports Expired
54.7 KB
sha256:af420137a2571b42c85e97f1b004b58fbf2ca874a4c83102eea985317d715412
python-tagged-unittest-gate-batch3-linux-amd64-jdk-latest_test_reports Expired
56.3 KB
sha256:eefb8cf26e15ee3caab99b992b2cf2082ac8eeb66d21e708274eb39a8d750bb5
python-tagged-unittest-gate-batch4-linux-aarch64-jdk-latest_test_reports Expired
54.6 KB
sha256:76021a36a169f5c0c42df1bcbe31921e3993fb1380ae56a9d708a94de4a986fd
python-tagged-unittest-gate-batch4-linux-amd64-jdk-latest_test_reports Expired
56.1 KB
sha256:206c655e51ee2b0a4fc2d416112c2121900452d77e3a5b88332e2576026ab4d8
python-tagged-unittest-gate-batch5-linux-aarch64-jdk-latest_test_reports Expired
47.6 KB
sha256:f2059ea3bb961375ae7c4257c0c7f982fc239ef2315698d50b3124b7adcab9db
python-tagged-unittest-gate-batch5-linux-amd64-jdk-latest_test_reports Expired
48.6 KB
sha256:c8573993b9681393796e96d7f3a6f3b416ab5d5fd80f40757babc7c3d52b08f3
python-tagged-unittest-gate-batch6-linux-aarch64-jdk-latest_test_reports Expired
26.5 KB
sha256:76506db63fbd2c4d73bc6a4ab8f633791575d3af949249eeac9ff20990f0280b
python-tagged-unittest-gate-batch6-linux-amd64-jdk-latest_test_reports Expired
27.2 KB
sha256:38316b1ecafe1befa78cdfba9872fb1dea274a8eb829f787ffec6ade0c0ba4d6
python-tagged-unittest-gate-batch7-linux-aarch64-jdk-latest_test_reports Expired
63 KB
sha256:c72f124bd403e34c151e7316a5385b7f4a0d75bc05ab7eea5ff99a1d3a33eaeb
python-tagged-unittest-gate-batch7-linux-amd64-jdk-latest_test_reports Expired
64.6 KB
sha256:ee3270f6e724fc37c3ae44673f1296e3abc86e8826241cce0499a687cc388eab
python-tagged-unittest-gate-batch8-linux-aarch64-jdk-latest_test_reports Expired
89 KB
sha256:1cbf67476840a60f55cdbd598ae3f595ddd5b47d79cd2d07ea270e4718abab03
python-tagged-unittest-gate-batch8-linux-amd64-jdk-latest_test_reports Expired
93.3 KB
sha256:12d9570ac186ab0198547852d7ba62473c63b3045a1bd264fa538bd97949ec76
python-unittest-arrow-storage-gate-linux-amd64-jdk-latest_test_reports Expired
39.1 KB
sha256:5169261b8b0fca71cddd4c0ce3203e58b050fcea2968620f4e26b99fadde9a9d
python-unittest-gate-linux-aarch64-jdk-latest_test_reports Expired
42.1 KB
sha256:910c58a2a5c296cd8b8970ac1a23ba080b31b37c42106c41741dbdf476b5af43
python-unittest-gate-linux-amd64-jdk-latest_test_reports Expired
39.5 KB
sha256:26bb137a82efda11d28fec8a62305f8003add4231d3731a274600af6ffb15456
python-unittest-jython-gate-linux-amd64-jdk-latest_test_reports Expired
1.39 KB
sha256:a1d7e233a82a2a48823f41dc6c1bd1a88bee15659b7eaefb02d99b43f13fcf68
python-unittest-multi-context-gate-linux-amd64-jdk-latest_test_reports Expired
39.4 KB
sha256:07d0801b5c3ad04ce87f7d046628a8af109e58aed53506e5f33233f89f00ac2d
python-unittest-native-debug-build-gate-linux-amd64-jdk-latest_test_reports Expired
42.3 KB
sha256:2dca259b2537c6c0f7dbbb44931c62c2a73178dd014cf1398f899037b14c9c1d
python-unittest-standalone-gate-batch1-windows-amd64-jdk-latest_logs Expired
65.7 KB
sha256:dbf5a64088b9b334990f77adfa7368a550dc1d6b107208dd3056bfee57732039
python-unittest-standalone-gate-batch2-windows-amd64-jdk-latest_logs Expired
65.9 KB
sha256:aab91acad3999d655cbe2ca0d1b8722dc198bc94721949ad0799a0b4f800f78e
python-unittest-standalone-gate-linux-aarch64-jdk-latest_logs Expired
73.8 KB
sha256:88a45a6466fd39de0287b4afcdf809c9d16f805530020932f2c58a3716f9ba95
python-unittest-standalone-gate-linux-amd64-jdk-latest_logs Expired
62 KB
sha256:debe2775586f8a3dceaa13dd24d63b9e204ee8bc859098b64f116b7a32d1cb0e