Skip to content

Updated version of NodeFootprintAnalyzer #147

Updated version of NodeFootprintAnalyzer

Updated version of NodeFootprintAnalyzer #147

Triggered via pull request March 17, 2026 11:02
Status Failure
Total duration 1h 14m 4s
Artifacts 4

ci-unittests.yml

on: pull_request
build-standalone-artifacts  /  generate-tier1
13s
build-standalone-artifacts / generate-tier1
build-standalone-artifacts  /  generate-tier2
10s
build-standalone-artifacts / generate-tier2
build-standalone-artifacts  /  generate-tier3
10s
build-standalone-artifacts / generate-tier3
Matrix: build-standalone-artifacts / tier1
Matrix: build-standalone-artifacts / tier2
Matrix: build-standalone-artifacts / tier3
run-tests  /  generate-tier1
run-tests / generate-tier1
run-tests  /  generate-tier2
run-tests / generate-tier2
run-tests  /  generate-tier3
run-tests / generate-tier3
Matrix: run-tests / tier1
Waiting for pending jobs
Matrix: run-tests / tier2
Waiting for pending jobs
Matrix: run-tests / tier3
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

1 error and 5 warnings
build-standalone-artifacts / tier1 (style-gate-linux-amd64-jdk-latest, 7.74.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. 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.74.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. 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.74.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. 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.74.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. 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.74.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/

Artifacts

Produced during runtime
Name Size Digest
graalpy-jvm-standalonelinux Expired
137 MB
sha256:e2677c7a1ef5aeb2fd16bbfb8b1d9e5ce5dda71efb147d51425fe987e27c7fbd
graalpy-native-standalonelinux Expired
166 MB
sha256:d25461e1e42503fcb9755c74dac032513146e5fa93ac53cd601e06a12f53b9b8
graalpy-native-standalonelinux_aarch64 Expired
163 MB
sha256:19cc947913faa8daf15038489262b32fcda2762432816b72603c8ece78293534
graalpy-native-standalonewindows Expired
107 MB
sha256:7cecea76ac39b52ae038117cd353d253e1eacbab4bcd491059ece1b829553ac3