Skip to content

DST

DST #3410

Triggered via schedule September 25, 2024 23:02
Status Failure
Total duration 1h 16m 23s
Artifacts 4

dst.yaml

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

Annotations

15 errors and 1 warning
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 (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 (lazy, 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 (lazy, sqlite, 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 (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, postgres, 2)
The hosted runner: GitHub Actions 3 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 (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.
build
Cache save failed.

Artifacts

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