DST #3451
Annotations
12 errors and 2 warnings
dst (default, sqlite, 1)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
dst (default, sqlite, 1)
Process completed with exit code 143.
|
dst (default, postgres, 2)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
dst (default, postgres, 2)
Process completed with exit code 143.
|
dst (lazy, postgres, 1)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
dst (lazy, postgres, 1)
Process completed with exit code 143.
|
dst (lazy, sqlite, 2)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
dst (lazy, sqlite, 2)
Process completed with exit code 143.
|
dst (default, postgres, 1)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
dst (default, postgres, 1)
Process completed with exit code 143.
|
dst (default, sqlite, 2)
The hosted runner: GitHub Actions 55 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.
|
dst (lazy, sqlite, 1)
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.
|
build
Cache save failed.
|
dst (lazy, postgres, 2)
Received request to deprovision: The request was cancelled by the remote provider.
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
fault-postgres-1-logs
|
198 KB |
|
fault-postgres-2-logs
|
198 KB |
|
fault-sqlite-1-logs
|
198 KB |
|
fault-sqlite-2-logs
|
198 KB |
|