DST

DST #5132

Sign in to view logs

Triggered via schedule December 7, 2024 02:27

avillega

main

Status Failure

Total duration 1h 30m 5s

Artifacts 4

dst.yaml

on: schedule

Matrix: dst

Matrix: diff

Annotations

14 errors and 1 warning

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 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, 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 (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 (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 hosted runner: GitHub Actions 14 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 60 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.

Cache save failed.

Artifacts

Produced during runtime

Name	Size
fault-postgres-1-logs Expired	241 KB
fault-postgres-2-logs Expired	241 KB
fault-sqlite-1-logs Expired	241 KB
fault-sqlite-2-logs Expired	241 KB