Skip to content

DST

DST #3399

Triggered via schedule September 25, 2024 12:03
Status Failure
Total duration 50m 6s
Artifacts 12

dst.yaml

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

Annotations

6 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, 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, postgres, 1)
The hosted runner: GitHub Actions 25 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, postgres, 2)
The hosted runner: GitHub Actions 28 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.

Artifacts

Produced during runtime
Name Size
fault-postgres-1-logs
241 KB
fault-postgres-2-logs
241 KB
fault-sqlite-1-logs
241 KB
fault-sqlite-2-logs
241 KB
lazy-postgres-1-logs
227 KB
lazy-postgres-1-visualization
1.32 MB
lazy-postgres-2-logs
227 KB
lazy-postgres-2-visualization
1.32 MB
lazy-sqlite-1-logs
227 KB
lazy-sqlite-1-visualization
1.32 MB
lazy-sqlite-2-logs
227 KB
lazy-sqlite-2-visualization
1.32 MB