Skip to content

Dry run xcms on bridge hubs to get forwarded xcms across the W<>R bridge #11245

Dry run xcms on bridge hubs to get forwarded xcms across the W<>R bridge

Dry run xcms on bridge hubs to get forwarded xcms across the W<>R bridge #11245

Triggered via pull request October 15, 2024 12:53
Status Failure
Total duration 16m 22s
Artifacts

tests-linux-stable.yml

on: pull_request
preflight  /  preflight
37s
preflight / preflight
preflight  /  ci-versions
1m 2s
preflight / ci-versions
Matrix: test-linux-stable-no-try-runtime
Matrix: test-linux-stable
test-linux-stable-int
4m 20s
test-linux-stable-int
test-linux-stable-runtime-benchmarks
6m 3s
test-linux-stable-runtime-benchmarks
All tests passed
0s
All tests passed
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 7 warnings
test-linux-stable-int
Process completed with exit code 1.
test-linux-stable (2/3, parity-oldlinux)
Process completed with exit code 1.
test-linux-stable-no-try-runtime (2/2)
Process completed with exit code 1.
test-linux-stable (2/3, parity-large)
Process completed with exit code 1.
test-linux-stable (3/3, parity-large)
Process completed with exit code 1.
test-linux-stable-no-try-runtime (1/2)
Process completed with exit code 1.
test-linux-stable (1/3, parity-large)
Process completed with exit code 1.
test-linux-stable-runtime-benchmarks
Process completed with exit code 1.
test-linux-stable (3/3, parity-oldlinux)
Process completed with exit code 1.
test-linux-stable (1/3, parity-oldlinux)
The self-hosted runner: gha-oldkernel-runner-7f1d lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
All tests passed
Process completed with exit code 1.
test-linux-stable-int
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.319.1. Please update to the latest version 2.320.0
test-linux-stable-no-try-runtime (2/2)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.319.1. Please update to the latest version 2.320.0
test-linux-stable (2/3, parity-large)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.319.1. Please update to the latest version 2.320.0
test-linux-stable (3/3, parity-large)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.319.1. Please update to the latest version 2.320.0
test-linux-stable-no-try-runtime (1/2)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.319.1. Please update to the latest version 2.320.0
test-linux-stable (1/3, parity-large)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.319.1. Please update to the latest version 2.320.0
test-linux-stable-runtime-benchmarks
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.319.1. Please update to the latest version 2.320.0