Skip to content
Validate Pull Request

Use WHvResetPartition on Windows instead of manual vCPU state reset #3611

Sign in to view logs

Use WHvResetPartition on Windows instead of manual vCPU state reset

Use WHvResetPartition on Windows instead of manual vCPU state reset #3611

Triggered via pull request March 13, 2026 16:56
@ludfjigludfjig
synchronize #1306
ludfjig:windows_scrub
Status Failure
Total duration 16m 1s
Artifacts 6

ValidatePullRequest.yml

on: pull_request
docs-pr
6s
docs-pr
update-guest-locks  /  update-guest-locks
update-guest-locks / update-guest-locks
spell check with typos
5s
spell check with typos
check license headers
6s
check license headers
Matrix: build-guests
code-checks  /  linux-checks
10m 52s
code-checks / linux-checks
code-checks  /  windows-checks
11m 4s
code-checks / windows-checks
Matrix: build-test
Matrix: fuzzing / fuzz
Matrix: run-examples
report-ci-status
4s
report-ci-status
Fit to window
Zoom out
Zoom in

Annotations

81 errors and 34 warnings
build-test (hyperv, intel, debug) / build-and-test
Process completed with exit code 1.
build-test (kvm, amd, debug) / build-and-test
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
build-test (mshv3, amd, release) / build-and-test
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
build-test (kvm, intel, debug) / build-and-test
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
build-test (hyperv-ws2025, amd, debug) / build-and-test
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
build-test (hyperv-ws2025, amd, debug) / build-and-test
The operation was canceled.
build-test (hyperv-ws2025, intel, debug) / build-and-test
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
build-test (hyperv-ws2025, intel, debug) / build-and-test
The operation was canceled.
build-test (hyperv-ws2025, amd, release) / build-and-test
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
build-test (hyperv-ws2025, amd, release) / build-and-test
The operation was canceled.
build-test (hyperv, amd, debug) / build-and-test
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
build-test (hyperv, amd, debug) / build-and-test
The operation was canceled.
build-test (kvm, intel, release) / build-and-test
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
build-test (kvm, intel, release) / build-and-test
The operation was canceled.
build-test (hyperv-ws2025, intel, release) / build-and-test
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
build-test (hyperv-ws2025, intel, release) / build-and-test
The operation was canceled.
build-test (kvm, amd, release) / build-and-test
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
build-test (kvm, amd, release) / build-and-test
The operation was canceled.
build-test (mshv3, amd, debug) / build-and-test
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
build-test (mshv3, amd, debug) / build-and-test
The operation was canceled.
build-test (hyperv, amd, release) / build-and-test
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
build-test (hyperv, amd, release) / build-and-test
The operation was canceled.
build-test (hyperv, intel, release) / build-and-test
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
build-test (hyperv, intel, release) / build-and-test
The operation was canceled.
build-test (mshv3, intel, debug) / build-and-test
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
build-test (mshv3, intel, debug) / build-and-test
The operation was canceled.
build-test (mshv3, intel, release) / build-and-test
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
build-test (mshv3, intel, release) / build-and-test
The operation was canceled.
run-examples (hyperv, amd, debug) / run-examples
Process completed with exit code 1.
run-examples (mshv3, amd, release) / run-examples
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
run-examples (mshv3, intel, release) / run-examples
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
run-examples (mshv3, amd, debug) / run-examples
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
run-examples (mshv3, intel, debug) / run-examples
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
run-examples (hyperv-ws2025, intel, debug) / run-examples
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
run-examples (hyperv-ws2025, intel, debug) / run-examples
The operation was canceled.
run-examples (hyperv-ws2025, amd, debug) / run-examples
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
run-examples (hyperv-ws2025, amd, debug) / run-examples
The operation was canceled.
run-examples (hyperv, intel, debug) / run-examples
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
run-examples (hyperv, intel, debug) / run-examples
The operation was canceled.
run-examples (hyperv-ws2025, intel, release) / run-examples
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
run-examples (hyperv-ws2025, intel, release) / run-examples
The operation was canceled.
run-examples (hyperv, intel, release) / run-examples
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
run-examples (hyperv, intel, release) / run-examples
The operation was canceled.
run-examples (hyperv, amd, release) / run-examples
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
run-examples (hyperv, amd, release) / run-examples
The operation was canceled.
run-examples (hyperv-ws2025, amd, release) / run-examples
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
run-examples (hyperv-ws2025, amd, release) / run-examples
The operation was canceled.
run-examples (kvm, intel, debug) / run-examples
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
run-examples (kvm, intel, debug) / run-examples
The operation was canceled.
run-examples (kvm, amd, release) / run-examples
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
run-examples (kvm, amd, release) / run-examples
The operation was canceled.
run-examples (kvm, intel, release) / run-examples
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
run-examples (kvm, intel, release) / run-examples
The operation was canceled.
run-examples (kvm, amd, debug) / run-examples
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
run-examples (kvm, amd, debug) / run-examples
The operation was canceled.
report-ci-status
Process completed with exit code 1.
Validate Pull Request
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
Validate Pull Request
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
Validate Pull Request
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
Validate Pull Request
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
Validate Pull Request
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
Validate Pull Request
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
Validate Pull Request
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
Validate Pull Request
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
Validate Pull Request
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
Validate Pull Request
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
Validate Pull Request
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
Validate Pull Request
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
Validate Pull Request
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
Validate Pull Request
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
Validate Pull Request
The strategy configuration was canceled because "run-examples.hyperv_amd_debug" failed
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv_intel_debug" failed
docs-pr
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@v3. 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-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. 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 (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. 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, 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. 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. 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. 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. 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. 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. 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. 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. 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, 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. 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, 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. 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, 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. 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, 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. 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, 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. 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. 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. 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, 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. 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. 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, 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. 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, 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.05 MB
sha256:9d7cffe837d36fffd63ed8ea12266c38da0c2de28a8606774f1702090e1f7626
c-guests-release Expired
440 KB
sha256:816b221dd6f5af13bb7b3136fa3e0a08ef579d0fb5518bf79365eb5a19fa743b
interface-wasm Expired
1.19 KB
sha256:935520383a3b6daa2fe8cbd56e281a03d3b6af6b94f66ec274c6537e8f4ee0d8
rust-guests-debug Expired
3.1 MB
sha256:b1dcce59b1540dd41fa60396becb280a9f31bdcd03f9a9e3fa85123b01a8120c
rust-guests-release Expired
302 KB
sha256:48344e8c2ddd5b504d1fb264a9003024d7d46dc8360da9c98338635defe9733f
twoworlds-wasm Expired
363 Bytes
sha256:e2b0c1940273512025b91754c90ff3a03443ac624ba9eea7430a430abdf50e37