Skip to content

DST

DST #4533

Triggered via schedule November 11, 2024 15:02
Status Failure
Total duration 50m 5s
Artifacts 4

dst.yaml

on: schedule
Matrix: dst
Matrix: diff
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 3 warnings
dst (lazy, 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 (lazy, postgres, 2)
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, 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 (default, sqlite, 2)
Process completed with exit code 143.
dst (default, sqlite, 1)
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
dst (lazy, postgres, 1)
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
dst (lazy, sqlite, 1)
The hosted runner: GitHub Actions 57 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 (default, postgres, 1)
Received request to deprovision: The request was cancelled by the remote provider.
dst (default, postgres, 2)
Received request to deprovision: The request was cancelled by the remote provider.

Artifacts

Produced during runtime
Name Size
fault-postgres-1-logs
332 KB
fault-postgres-2-logs
332 KB
fault-sqlite-1-logs
332 KB
fault-sqlite-2-logs
332 KB