DST

DST #7298

Triggered via schedule March 6, 2025 23:01

avillega

⁠ 7195f7f

main

Status Failure

Total duration 6m 6s

Artifacts 4

dst.yaml

on: schedule

build

33s

values

Matrix: dst

Matrix: diff

Annotations

16 errors and 7 warnings

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 (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 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, 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, 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.

Magic Nix Cache is deprecated: .github/workflows/cicd.yaml#L111

Magic Nix Cache has been deprecated due to a change in the underlying GitHub APIs and will stop working on 1 February 2025. To continue caching Nix builds in GitHub Actions, use FlakeHub Cache instead. Replace... uses: DeterminateSystems/magic-nix-cache-action@v9 ...with... uses: DeterminateSystems/flakehub-cache-action@v9 For more details: https://dtr.mn/magic-nix-cache-eol

Magic Nix Cache is deprecated: .github/workflows/cicd.yaml#L149