feat(guest): replace musl with picolibc #3870
andreiltdValidatePullRequest.yml
on: pull_request
docs-pr
8s
update-guest-locks
/
update-guest-locks
Matrix: build-guests
code-checks
/
linux-checks
11m 10s
code-checks
/
windows-checks
10m 7s
Matrix: build-test
Matrix: fuzzing / fuzz
Matrix: run-examples
report-ci-status
2s
Annotations
76 errors and 28 warnings
|
build-test (mshv3, amd, release) / build-and-test
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
run-examples (mshv3, amd, debug) / run-examples
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
run-examples (mshv3, amd, release) / run-examples
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
build-test (mshv3, intel, release) / build-and-test
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
build-test (mshv3, intel, debug) / build-and-test
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
run-examples (mshv3, intel, debug) / run-examples
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
run-examples (kvm, amd, debug) / run-examples
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
run-examples (kvm, amd, debug) / run-examples
The operation was canceled.
|
|
run-examples (hyperv-ws2025, amd, release) / run-examples
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
run-examples (hyperv-ws2025, amd, release) / run-examples
The operation was canceled.
|
|
build-test (hyperv-ws2025, amd, debug) / build-and-test
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
build-test (hyperv-ws2025, amd, debug) / build-and-test
The operation was canceled.
|
|
fuzzing / fuzz (fuzz_host_print)
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
fuzzing / fuzz (fuzz_host_print)
The operation was canceled.
|
|
code-checks / linux-checks
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
code-checks / linux-checks
The operation was canceled.
|
|
run-examples (hyperv-ws2025, intel, release) / run-examples
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
run-examples (hyperv-ws2025, intel, release) / run-examples
The operation was canceled.
|
|
run-examples (kvm, amd, release) / run-examples
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
run-examples (kvm, amd, release) / run-examples
The operation was canceled.
|
|
run-examples (kvm, intel, debug) / run-examples
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
run-examples (kvm, intel, debug) / run-examples
The operation was canceled.
|
|
run-examples (hyperv-ws2025, intel, debug) / run-examples
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
run-examples (hyperv-ws2025, intel, debug) / run-examples
The operation was canceled.
|
|
fuzzing / fuzz (fuzz_guest_call)
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
fuzzing / fuzz (fuzz_guest_call)
The operation was canceled.
|
|
build-test (hyperv-ws2025, amd, release) / build-and-test
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
build-test (hyperv-ws2025, amd, release) / build-and-test
The operation was canceled.
|
|
build-test (kvm, amd, debug) / build-and-test
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
build-test (kvm, amd, debug) / build-and-test
The operation was canceled.
|
|
run-examples (hyperv-ws2025, amd, debug) / run-examples
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
run-examples (hyperv-ws2025, amd, debug) / run-examples
The operation was canceled.
|
|
build-test (kvm, intel, debug) / build-and-test
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
build-test (kvm, intel, debug) / build-and-test
The operation was canceled.
|
|
build-test (hyperv-ws2025, intel, release) / build-and-test
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
build-test (hyperv-ws2025, intel, release) / build-and-test
The operation was canceled.
|
|
build-test (kvm, amd, release) / build-and-test
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
build-test (kvm, amd, release) / build-and-test
The operation was canceled.
|
|
build-test (kvm, intel, release) / build-and-test
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
build-test (kvm, intel, release) / build-and-test
The operation was canceled.
|
|
fuzzing / fuzz (fuzz_host_call)
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
fuzzing / fuzz (fuzz_host_call)
The operation was canceled.
|
|
fuzzing / fuzz (fuzz_guest_trace)
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
fuzzing / fuzz (fuzz_guest_trace)
The operation was canceled.
|
|
build-test (hyperv-ws2025, intel, debug) / build-and-test
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
build-test (hyperv-ws2025, intel, debug) / build-and-test
The operation was canceled.
|
|
fuzzing / fuzz (fuzz_guest_estimate_trace_event)
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
fuzzing / fuzz (fuzz_guest_estimate_trace_event)
The operation was canceled.
|
|
build-test (mshv3, amd, debug) / build-and-test
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
build-test (mshv3, amd, debug) / build-and-test
The operation was canceled.
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
report-ci-status
Process completed with exit code 1.
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
Validate Pull Request
Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/831/merge exists
|
|
build-guests (debug) / build-guests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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-guests (release) / build-guests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/
|
|
code-checks / windows-checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/
|
|
code-checks / windows-checks
cargo-binstall fallback does not support prebuilt binaries for cargo-hyperlight@0.1.8 on this platform (x86_64); use 'cargo-install' fallback instead
|
|
run-examples (mshv3, intel, release) / run-examples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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-examples (kvm, intel, release) / run-examples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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-examples (kvm, amd, debug) / run-examples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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-examples (hyperv-ws2025, amd, release) / run-examples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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-test (hyperv-ws2025, amd, debug) / build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/
|
|
fuzzing / fuzz (fuzz_host_print)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/
|
|
code-checks / linux-checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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-examples (hyperv-ws2025, intel, release) / run-examples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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-examples (kvm, amd, release) / run-examples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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-examples (kvm, intel, debug) / run-examples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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-examples (hyperv-ws2025, intel, debug) / run-examples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/
|
|
fuzzing / fuzz (fuzz_guest_call)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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-test (hyperv-ws2025, amd, release) / build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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-test (kvm, amd, debug) / build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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-examples (hyperv-ws2025, amd, debug) / run-examples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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-test (kvm, intel, debug) / build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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-test (hyperv-ws2025, intel, release) / build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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-test (kvm, amd, release) / build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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-test (kvm, intel, release) / build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/
|
|
fuzzing / fuzz (fuzz_host_call)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/
|
|
fuzzing / fuzz (fuzz_guest_trace)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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-test (hyperv-ws2025, intel, debug) / build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/
|
|
fuzzing / fuzz (fuzz_guest_estimate_trace_event)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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-test (mshv3, amd, debug) / build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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 | |
|---|---|---|---|
|
c-guests-debug
Expired
|
2.09 MB |
sha256:483396eb95625c01b1891cf58bde476fe8f23cb63db1abe09fc69b6e50fcbce8
|
|
|
c-guests-release
Expired
|
442 KB |
sha256:f71ced98644f8e387fef0395bcaa045764bc1db226615ff225a03c18546df2ff
|
|
|
interface-wasm
Expired
|
1.19 KB |
sha256:ba13790fb55b74f54acd7a504c7bd9293500c7eb2be68cb4ba2e38934df70e9c
|
|
|
rust-guests-debug
Expired
|
3.15 MB |
sha256:a236ad860bc6b7e8f4aec53e884dcf61ea45a112dbe430b0e590352314934384
|
|
|
rust-guests-release
Expired
|
300 KB |
sha256:c0d6d74e340b8d34110ada367be03f82ffa162cd2852453150e2c59f40bc1ad9
|
|
|
twoworlds-wasm
Expired
|
364 Bytes |
sha256:08d811eea9b3d76f0e3e8e6968754393fefc9bb5e23f5e2de4e061561a260688
|
|