[ci-unrelated] CI failures unrelated to PR changes

[bketelsen]

Auto-created by Yeti ci-fixer

This issue tracks CI failures that are unrelated to the PRs they occurred on (flakey tests, runner issues, pre-existing failures).
Each occurrence is logged below.

[bketelsen]

— Automated by Yeti —

log:truncated-no-failure — 2026-03-20T18:16:44.445Z

Observed on: PR #6 (chore(deps): bump docker/metadata-action from 5.10.0 to 6.0.0)
Reason: The log is truncated during the checkout/submodule setup phase and shows no actual failure. No error message is present in the provided log, and the steps shown (checkout, submodule init) are unrelated to the docker/metadata-action version bump.
Failing run: https://github.com/frostyard/cayo/actions/runs/22822451299/job/66197254100

Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6545412Z Current runner version: '2.332.0'
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6572790Z ##[group]Runner Image Provisioner
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6573859Z Hosted Compute Agent
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6574587Z Version: 20260213.493
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6575245Z Commit: 5c115507f6dd24b8de37d8bbe0bb4509d0cc0fa3
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6575927Z Build Date: 2026-02-13T00:28:41Z
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6576671Z Worker ID: {237b6c8f-918b-47b5-b6b1-76d0c72d202e}
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6577366Z Azure Region: eastus2
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6578225Z ##[endgroup]
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6580498Z ##[group]Operating System
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6581426Z Ubuntu
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6582088Z 24.04.3
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6583138Z LTS
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6583694Z ##[endgroup]
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6584214Z ##[group]Runner Image
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6584854Z Image: ubuntu-24.04
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6585366Z Version: 20260302.42.1
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6586635Z Included Software: https://github.com/actions/runner-images/blob/ubuntu24/20260302.42/images/ubuntu/Ubuntu2404-Readme.md
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6588081Z Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu24%2F20260302.42
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6588979Z ##[endgroup]
Build and push image	UNKNOWN STEP	2026-03-08T13:52:34.6590106Z ##[group]GITHUB_TOKEN Permissions
Build and push 

[bketelsen]

— Automated by Yeti —

ci:log-truncated — 2026-03-20T18:16:45.189Z

Observed on: PR #5 (chore(deps): bump docker/login-action from 3.6.0 to 4.0.0)
Reason: The log is truncated during the checkout/submodule setup phase and shows no actual failure — just standard CI runner initialization. No error message is present, so this appears to be an incomplete log or a runner infrastructure issue, not a failure caused by the docker/login-action version bump.
Failing run: https://github.com/frostyard/cayo/actions/runs/22822450411/job/66197252063

Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6248224Z Current runner version: '2.332.0'
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6280372Z ##[group]Runner Image Provisioner
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6281299Z Hosted Compute Agent
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6281887Z Version: 20260213.493
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6282456Z Commit: 5c115507f6dd24b8de37d8bbe0bb4509d0cc0fa3
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6283223Z Build Date: 2026-02-13T00:28:41Z
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6283867Z Worker ID: {8ddc589d-13f8-4103-a01b-0e117a00a33c}
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6284589Z Azure Region: northcentralus
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6285113Z ##[endgroup]
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6286740Z ##[group]Operating System
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6287358Z Ubuntu
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6287793Z 24.04.3
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6288348Z LTS
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6288803Z ##[endgroup]
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6289285Z ##[group]Runner Image
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6290248Z Image: ubuntu-24.04
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6290778Z Version: 20260302.42.1
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6291986Z Included Software: https://github.com/actions/runner-images/blob/ubuntu24/20260302.42/images/ubuntu/Ubuntu2404-Readme.md
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6293421Z Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu24%2F20260302.42
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6294272Z ##[endgroup]
Build and push image	UNKNOWN STEP	2026-03-08T13:52:31.6295434Z ##[group]GITHUB_TOKEN Permissions
Build an

[bketelsen]

— Automated by Yeti —

Implementation Plan

Implementation Plan for Issue #7

Analysis

Both CI failures documented in this issue are GitHub Actions runner infrastructure problems, not code issues:

• Both occurred on 2026-03-08 at nearly the same time (~13:52 UTC) on different PRs (chore(deps): bump docker/login-action from 3.6.0 to 4.0.0 #5 and chore(deps): bump docker/metadata-action from 5.10.0 to 6.0.0 #6)
• Both logs truncate during runner initialization, before any workflow steps execute
• No error messages are present — the logs simply stop mid-output
• The failures are unrelated to the dependency bumps in those PRs

Since the truncation happens during runner bootstrapping (before the Checkout step even begins), no amount of in-workflow retry logic would help — the runner itself failed to initialize.

Recommendation: No code changes needed

This issue is a tracking/observability issue, not an actionable bug. The correct response is:

1. Re-run the failed jobs on PRs chore(deps): bump docker/login-action from 3.6.0 to 4.0.0 #5 and chore(deps): bump docker/metadata-action from 5.10.0 to 6.0.0 #6 via GitHub UI (or gh run rerun)
2. Close this issue or leave it open as a log if the pattern recurs, since there's no code fix

Optional improvement (low priority)

If these runner failures become frequent, one minor resilience improvement could be made:

File: .github/workflows/build.yml

Add a job-level retry by setting timeout-minutes to catch hung runners, and potentially adding a second workflow that auto-reruns failed jobs. However:

• GitHub Actions doesn't natively support job-level retries
• Third-party rerun actions (e.g., rerun-failed-jobs) add complexity for marginal benefit
• The current concurrency configuration with cancel-in-progress: true (line 27) is already reasonable

Risks

• No risk from inaction — these are one-off runner failures, not a systemic issue
• Risk from over-engineering — adding retry/rerun automation for rare infrastructure blips adds maintenance burden without clear benefit

Suggested next steps

1. Re-run the two failed workflow runs:

   gh run rerun 22822451299 --repo frostyard/cayo
   gh run rerun 22822450411 --repo frostyard/cayo
   

2. If both pass on retry, close the issue as resolved (infrastructure flake)
3. If the pattern recurs, revisit adding automated rerun logic

No PR is needed for this issue.