fix: Handle KeyboardInterrupt, SIGINT, SIGTERM gracefully #1053
Triggered via pull request
August 6, 2024 14:32
eddiebergman
Status
Failure
Total duration
1h 54m 47s
Artifacts
–
Annotations
14 errors
|
tests (3.11, windows-latest)
Process completed with exit code 1.
|
|
tests (3.10, ubuntu-latest)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
tests (3.10, ubuntu-latest)
The operation was canceled.
|
|
tests (3.9, ubuntu-latest)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
tests (3.9, ubuntu-latest)
The operation was canceled.
|
|
tests (3.8, ubuntu-latest)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
tests (3.8, ubuntu-latest)
The operation was canceled.
|
|
tests (3.8, windows-latest)
Process completed with exit code 1.
|
|
tests (3.9, windows-latest)
Process completed with exit code 1.
|
|
tests (3.10, windows-latest)
Process completed with exit code 1.
|
|
tests (3.10, macos-latest)
The hosted runner: GitHub Actions 17 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.
|
|
tests (3.9, macos-latest)
The hosted runner: GitHub Actions 4 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.
|
|
tests (3.8, macos-latest)
The hosted runner: GitHub Actions 19 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.
|
|
tests (3.8, macos-latest)
[notice] A new release of pip is available: 21.1.1 -> 24.2
[notice] To update, run: python3.8 -m pip install --upgrade pip
|