[coding] ZODA reject duplicate shards + interval search #21964
cronokirbyslow.yml
on: pull_request
Matrix: conformance
Matrix: Tests
Matrix: Unsafe
Matrix: Benchmarks
Matrix: Fuzz
Annotations
89 errors, 65 warnings, and 8 notices
|
Miri Tests (partition: 1/8)
Process completed with exit code 104.
|
|
Miri Tests (partition: 5/8)
The strategy configuration was canceled because "Unsafe._1" failed
|
|
Miri Tests (partition: 3/8)
The strategy configuration was canceled because "Unsafe._1" failed
|
|
Miri Tests (partition: 7/8)
The strategy configuration was canceled because "Unsafe._1" failed
|
|
Miri Tests (partition: 4/8)
The strategy configuration was canceled because "Unsafe._1" failed
|
|
Miri Tests (partition: 8/8)
The strategy configuration was canceled because "Unsafe._1" failed
|
|
Miri Tests (partition: 2/8)
The strategy configuration was canceled because "Unsafe._1" failed
|
|
Miri Tests (partition: 2/8)
Process completed with exit code 104.
|
|
Miri Tests (partition: 6/8)
The strategy configuration was canceled because "Unsafe._1" failed
|
|
Miri Tests (partition: 6/8)
The operation was canceled.
|
|
Breaking Changes (x86_64) (partition: 8/8)
The strategy configuration was canceled because "conformance.x86_64_5" failed
|
|
Breaking Changes (x86_64) (partition: 3/8)
The strategy configuration was canceled because "conformance.x86_64_5" failed
|
|
Breaking Changes (arm64) (partition: 2/8)
The strategy configuration was canceled because "conformance.x86_64_5" failed
|
|
Breaking Changes (arm64) (partition: 4/8)
The strategy configuration was canceled because "conformance.x86_64_5" failed
|
|
Breaking Changes (arm64) (partition: 5/8)
The strategy configuration was canceled because "conformance.x86_64_5" failed
|
|
Breaking Changes (x86_64) (partition: 5/8)
Process completed with exit code 101.
|
|
Breaking Changes (x86_64) (partition: 4/8)
The strategy configuration was canceled because "conformance.x86_64_5" failed
|
|
Breaking Changes (arm64) (partition: 6/8)
The strategy configuration was canceled because "conformance.x86_64_5" failed
|
|
Breaking Changes (x86_64) (partition: 2/8)
The strategy configuration was canceled because "conformance.x86_64_5" failed
|
|
Breaking Changes (arm64) (partition: 3/8)
The strategy configuration was canceled because "conformance.x86_64_5" failed
|
|
Breaking Changes (x86_64) (partition: 6/8)
The strategy configuration was canceled because "conformance.x86_64_5" failed
|
|
Breaking Changes (arm64) (partition: 8/8)
The strategy configuration was canceled because "conformance.x86_64_5" failed
|
|
Breaking Changes (arm64) (partition: 7/8)
The strategy configuration was canceled because "conformance.x86_64_5" failed
|
|
Breaking Changes (x86_64) (partition: 7/8)
The strategy configuration was canceled because "conformance.x86_64_5" failed
|
|
Breaking Changes (x86_64) (partition: 1/8)
The strategy configuration was canceled because "conformance.x86_64_5" failed
|
|
Breaking Changes (x86_64) (partition: 1/8)
The operation was canceled.
|
|
Breaking Changes (arm64) (partition: 1/8)
The strategy configuration was canceled because "conformance.x86_64_5" failed
|
|
Breaking Changes (arm64) (partition: 1/8)
The operation was canceled.
|
|
Tests (os: windows-latest, flags: "") (partition: 5/8)
Process completed with exit code 1.
|
|
Tests (os: ubuntu-latest, flags: "--features commonware-runtime/iouring-storage") (partition: 1/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "") (partition: 1/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--no-default-features") (partition: 2/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--features commonware-runtime/iouring-network") (partition: 1/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--features commonware-runtime/iouring-network") (partition: 2/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--no-default-features") (partition: 1/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--no-default-features") (partition: 3/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--features commonware-runtime/iouring-storage") (partition: 2/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--features commonware-runtime/iouring-network") (partition: 3/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--features commonware-runtime/iouring-storage") (partition: 3/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "") (partition: 2/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--no-default-features") (partition: 4/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--no-default-features") (partition: 5/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--features commonware-runtime/iouring-network") (partition: 7/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--features commonware-runtime/iouring-storage") (partition: 4/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "") (partition: 5/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--features commonware-runtime/iouring-storage") (partition: 6/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--features commonware-runtime/iouring-storage") (partition: 5/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--features commonware-runtime/iouring-storage") (partition: 8/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--features commonware-runtime/iouring-network") (partition: 5/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--features commonware-runtime/iouring-network") (partition: 6/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "") (partition: 4/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--features commonware-runtime/iouring-storage") (partition: 7/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "") (partition: 6/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "") (partition: 7/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "") (partition: 8/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--features commonware-runtime/iouring-network") (partition: 8/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: macos-latest, flags: "") (partition: 3/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--no-default-features") (partition: 8/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: macos-latest, flags: "") (partition: 6/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--no-default-features") (partition: 7/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: macos-latest, flags: "") (partition: 7/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: macos-latest, flags: "") (partition: 5/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: macos-latest, flags: "") (partition: 2/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: macos-latest, flags: "") (partition: 4/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: macos-latest, flags: "") (partition: 1/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: macos-latest, flags: "") (partition: 8/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "") (partition: 3/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "") (partition: 3/8)
The operation was canceled.
|
|
Tests (os: windows-latest, flags: "") (partition: 6/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: windows-latest, flags: "") (partition: 6/8)
The operation was canceled.
|
|
Tests (os: windows-latest, flags: "") (partition: 8/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: windows-latest, flags: "") (partition: 8/8)
The operation was canceled.
|
|
Tests (os: windows-latest, flags: "") (partition: 4/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: windows-latest, flags: "") (partition: 4/8)
The operation was canceled.
|
|
Tests (os: windows-latest, flags: "") (partition: 3/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: windows-latest, flags: "") (partition: 3/8)
The operation was canceled.
|
|
Tests (os: windows-latest, flags: "") (partition: 1/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: windows-latest, flags: "") (partition: 1/8)
The operation was canceled.
|
|
Tests (os: windows-latest, flags: "") (partition: 2/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: windows-latest, flags: "") (partition: 2/8)
The operation was canceled.
|
|
Tests (os: windows-latest, flags: "") (partition: 7/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: windows-latest, flags: "") (partition: 7/8)
The operation was canceled.
|
|
Tests (os: ubuntu-latest, flags: "--features commonware-runtime/iouring-network") (partition: 4/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--features commonware-runtime/iouring-network") (partition: 4/8)
The operation was canceled.
|
|
Tests (os: ubuntu-latest, flags: "--no-default-features") (partition: 6/8)
The strategy configuration was canceled because "Tests.windows-latest_5" failed
|
|
Tests (os: ubuntu-latest, flags: "--no-default-features") (partition: 6/8)
The operation was canceled.
|
|
Unsafe-Tests
Process completed with exit code 1.
|
|
Breaking Changes
Process completed with exit code 1.
|
|
Slow-Tests
Process completed with exit code 1.
|
|
Benchmarks (commonware-math)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Benchmarks (commonware-math)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Miri Tests (partition: 1/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Miri Tests (partition: 1/8)
cargo-nextest@0.9.133 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Miri Tests (partition: 1/8)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Miri Tests (partition: 2/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Miri Tests (partition: 2/8)
cargo-nextest@0.9.133 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Miri Tests (partition: 2/8)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Miri Tests (partition: 6/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Benchmarks (commonware-utils)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Benchmarks (commonware-utils)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Breaking Changes (x86_64) (partition: 5/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Breaking Changes (x86_64) (partition: 5/8)
cargo-nextest@0.9.133 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Breaking Changes (x86_64) (partition: 5/8)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Breaking Changes (x86_64) (partition: 1/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Breaking Changes (x86_64) (partition: 1/8)
cargo-nextest@0.9.133 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Breaking Changes (x86_64) (partition: 1/8)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Breaking Changes (arm64) (partition: 1/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Breaking Changes (arm64) (partition: 1/8)
cargo-nextest@0.9.133 for 'aarch64_macos' is not supported; fallback to cargo-binstall
|
|
Breaking Changes (arm64) (partition: 1/8)
just@1.43.0 for 'aarch64_macos' is not supported; fallback to cargo-binstall
|
|
Fuzz (codec/fuzz)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0400d5f644dc74513175e3cd8d07132dd4860809, actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Fuzz (codec/fuzz)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Tests (os: windows-latest, flags: "") (partition: 5/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Tests (os: windows-latest, flags: "") (partition: 5/8)
cargo-nextest@0.9.133 for 'x86_64_windows' is not supported; fallback to cargo-binstall
|
|
Tests (os: windows-latest, flags: "") (partition: 5/8)
just@1.43.0 for 'x86_64_windows' is not supported; fallback to cargo-binstall
|
|
Tests (os: ubuntu-latest, flags: "") (partition: 3/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Tests (os: windows-latest, flags: "") (partition: 6/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955. 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/
|
|
Tests (os: windows-latest, flags: "") (partition: 8/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955. 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/
|
|
Tests (os: windows-latest, flags: "") (partition: 4/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955. 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/
|
|
Tests (os: windows-latest, flags: "") (partition: 3/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955. 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/
|
|
Tests (os: windows-latest, flags: "") (partition: 1/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955. 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/
|
|
Tests (os: windows-latest, flags: "") (partition: 2/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955. 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/
|
|
Tests (os: windows-latest, flags: "") (partition: 7/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955. 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/
|
|
Tests (os: ubuntu-latest, flags: "--features commonware-runtime/iouring-network") (partition: 4/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955. 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/
|
|
Tests (os: ubuntu-latest, flags: "--no-default-features") (partition: 6/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955. 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/
|
|
Fuzz (math/fuzz)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0400d5f644dc74513175e3cd8d07132dd4860809, actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Fuzz (math/fuzz)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Fuzz (coding/fuzz)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0400d5f644dc74513175e3cd8d07132dd4860809, actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Fuzz (coding/fuzz)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Fuzz (collector/fuzz)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0400d5f644dc74513175e3cd8d07132dd4860809, actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Fuzz (collector/fuzz)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Fuzz (runtime/fuzz)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0400d5f644dc74513175e3cd8d07132dd4860809, actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Fuzz (runtime/fuzz)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Fuzz (broadcast/fuzz)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0400d5f644dc74513175e3cd8d07132dd4860809, actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Fuzz (broadcast/fuzz)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Benchmarks (commonware-cryptography)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Benchmarks (commonware-cryptography)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Fuzz (stream/fuzz)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0400d5f644dc74513175e3cd8d07132dd4860809, actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Fuzz (stream/fuzz)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Fuzz (p2p/fuzz)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0400d5f644dc74513175e3cd8d07132dd4860809, actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Fuzz (p2p/fuzz)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Fuzz (cryptography/fuzz)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0400d5f644dc74513175e3cd8d07132dd4860809, actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Fuzz (cryptography/fuzz)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Benchmarks (commonware-storage, --features commonware-runtime/iouring-storage,test-traits, --cfg ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Benchmarks (commonware-storage, --features commonware-runtime/iouring-storage,test-traits, --cfg ...
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Benchmarks (commonware-storage, --features test-traits, --cfg full_bench)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Benchmarks (commonware-storage, --features test-traits, --cfg full_bench)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Fuzz (utils/fuzz)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0400d5f644dc74513175e3cd8d07132dd4860809, actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Fuzz (utils/fuzz)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Benchmarks (commonware-coding)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Benchmarks (commonware-coding)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Fuzz (storage/fuzz)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0400d5f644dc74513175e3cd8d07132dd4860809, actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Fuzz (storage/fuzz)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Fuzz (consensus/fuzz)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0400d5f644dc74513175e3cd8d07132dd4860809, actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. 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/
|
|
Fuzz (consensus/fuzz)
just@1.43.0 for 'x86_64_linux' is not supported; fallback to cargo-binstall
|
|
Tests (os: windows-latest, flags: "") (partition: 5/8)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Tests (os: windows-latest, flags: "") (partition: 6/8)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Tests (os: windows-latest, flags: "") (partition: 8/8)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Tests (os: windows-latest, flags: "") (partition: 4/8)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Tests (os: windows-latest, flags: "") (partition: 3/8)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Tests (os: windows-latest, flags: "") (partition: 1/8)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Tests (os: windows-latest, flags: "") (partition: 2/8)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Tests (os: windows-latest, flags: "") (partition: 7/8)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|