[Release|CI/CD] Fix audiences changelog template #13769
You are viewing an older attempt in the history of this workflow run.
View latest attempt.
Triggered via pull request
November 12, 2024 06:44
EgorPopelyaev
Status
Failure
Total duration
38m 40s
Artifacts
–
tests-linux-stable.yml
on: pull_request
preflight
/
preflight
42s
Matrix: test-linux-stable-no-try-runtime
Matrix: test-linux-stable
test-linux-stable-int
7m 19s
test-linux-stable-runtime-benchmarks
24m 18s
All tests passed
0s
Annotations
7 errors and 1 warning
|
test-linux-stable (2/3, parity-oldlinux)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
test-linux-stable (2/3, parity-oldlinux)
Process completed with exit code 1.
|
|
test-linux-stable (3/3, parity-oldlinux)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
test-linux-stable (3/3, parity-oldlinux)
Process completed with exit code 1.
|
|
test-linux-stable (1/3, parity-oldlinux)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
test-linux-stable (1/3, parity-oldlinux)
The self-hosted runner: gha-oldkernel-runner-n01f 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 (1/3, parity-oldlinux)
Docker pull failed with exit code 1, back off 7.698 seconds before retry.
|