Skip to content

feat: ARM64 runtime guards (SMT, CPU info, seccomp, UFFD) (#2259) #1342

feat: ARM64 runtime guards (SMT, CPU info, seccomp, UFFD) (#2259)

feat: ARM64 runtime guards (SMT, CPU info, seccomp, UFFD) (#2259) #1342

Triggered via push April 2, 2026 11:51
Status Success
Total duration 10m 53s
Artifacts 3

push-main.yml

on: push
Matrix: unit-tests / run-tests
unit-tests  /  Validate terraform
19s
unit-tests / Validate terraform
integration-tests  /  integration_tests
9m 47s
integration-tests / integration_tests
generated-code-check  /  run-check
4m 58s
generated-code-check / run-check
publish-test-results
58s
publish-test-results
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
unit-tests / Validate terraform
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hashicorp/setup-terraform@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
generated-code-check / run-check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hashicorp/setup-terraform@v3, jdx/mise-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
integration-tests / integration_tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
Integration Tests Results
5.68 KB
sha256:5217189e305c0c1185c66b392d5857f8bb92e1e0409404cc35b05e13afefd200
Service Logs
5.03 MB
sha256:15438cc75779855228a721ca63714594e0496e3e1100d1332e6cef44e1be08ab
e2b-dev~infra~I9M9J0.dockerbuild
27.6 KB
sha256:426b2392ff6d36eed40fd8d49c8702396129df9e71616d7cfabd038649136aa1