Skip to content
Tests

Bump to 7.2.0 #234

Sign in to view logs

Bump to 7.2.0

Bump to 7.2.0 #234

Triggered via pull request September 4, 2024 14:32
@BuonOmoBuonOmo
synchronize #405
bump-7-2
Status Failure
Total duration 5h 4m 2s
Artifacts –

tests.yml

on: pull_request
Matrix: test
Test Results
0s
Test Results
Fit to window
Zoom out
Zoom in

Annotations

30 errors
test (3.1, 16-master)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
test (3.1, 16-master)
The operation was canceled.
test (3.1, 14-master)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
test (3.1, 14-master)
The operation was canceled.
test (3.1, 12-master)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
test (3.1, 12-master)
The operation was canceled.
test (3.1, 13-master)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
test (3.1, 13-master)
The operation was canceled.
test (3.1, 15-master)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
test (3.1, 15-master)
The operation was canceled.
test (3.2, 14-master)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
test (3.2, 14-master)
The operation was canceled.
test (3.2, 13-master)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
test (3.2, 13-master)
The operation was canceled.
test (3.2, 12-master)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
test (3.2, 12-master)
The operation was canceled.
test (3.2, 15-master)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
test (3.2, 15-master)
The operation was canceled.
test (3.2, 16-master)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
test (3.2, 16-master)
The operation was canceled.
test (3.3, 12-master)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
test (3.3, 12-master)
The operation was canceled.
test (3.3, 13-master)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
test (3.3, 13-master)
The operation was canceled.
test (3.3, 14-master)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
test (3.3, 14-master)
The operation was canceled.
test (3.3, 15-master)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
test (3.3, 15-master)
The operation was canceled.
test (3.3, 16-master)
The hosted runner: GitHub Actions 20 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Test Results
Process completed with exit code 1.