Skip to content
test-isolate

test-isolate #394

Sign in to view logs

test-isolate

test-isolate #394

Triggered via schedule September 13, 2025 00:23
@slvDevslvDev
⁠ b34b0f7
master
Status Failure
Total duration 21m 39s
Artifacts –

test-isolate.yml

on: schedule
nextest  /  build matrices
5s
nextest / build matrices
Matrix: nextest / test
Fit to window
Zoom out
Zoom in

Annotations

16 errors and 8 notices
nextest / test integration (3/3) (x86_64-unknown-linux-gnu)
Process completed with exit code 100.
nextest / test integration (2/3) (x86_64-unknown-linux-gnu)
Process completed with exit code 100.
nextest / test integration (1/3) (x86_64-unknown-linux-gnu)
Process completed with exit code 100.
nextest / test integration (1/3) (aarch64-apple-darwin)
Process completed with exit code 100.
nextest / test integration (3/3) (aarch64-apple-darwin)
Process completed with exit code 100.
nextest / test integration (2/3) (x86_64-pc-windows-msvc)
Process completed with exit code 1.
nextest / test integration / issue-repros (2/2) (aarch64-apple-darwin)
Process completed with exit code 100.
nextest / test integration (1/3) (x86_64-pc-windows-msvc)
Process completed with exit code 1.
nextest / test integration (3/3) (x86_64-pc-windows-msvc)
Process completed with exit code 1.
nextest / test unit (x86_64-pc-windows-msvc)
Process completed with exit code 1.
nextest / test integration / external (1/2) (x86_64-unknown-linux-gnu)
Process completed with exit code 100.
nextest / test integration / issue-repros (2/2) (x86_64-unknown-linux-gnu)
Process completed with exit code 100.
nextest / test integration (2/3) (aarch64-apple-darwin)
Process completed with exit code 100.
nextest / test integration / issue-repros (2/2) (x86_64-pc-windows-msvc)
Process completed with exit code 1.
nextest / test integration / issue-repros (1/2) (x86_64-pc-windows-msvc)
Process completed with exit code 1.
nextest / test integration / external (1/2) (aarch64-apple-darwin)
Process completed with exit code 100.
nextest / test integration (2/3) (x86_64-pc-windows-msvc)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
nextest / test integration (1/3) (x86_64-pc-windows-msvc)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
nextest / test integration (3/3) (x86_64-pc-windows-msvc)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
nextest / test unit (x86_64-pc-windows-msvc)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
nextest / test integration / external (2/2) (x86_64-pc-windows-msvc)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
nextest / test integration / issue-repros (2/2) (x86_64-pc-windows-msvc)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
nextest / test integration / issue-repros (1/2) (x86_64-pc-windows-msvc)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
nextest / test integration / external (1/2) (x86_64-pc-windows-msvc)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677