Repository navigation

[ci] Build Gurnard scheduled run failed #4505

Open

Labels

ci-failurestage/010-actionable

bot

opened

on Nov 11, 2026

The scheduled run of Build Gurnard (.github/workflows/build-gurnard.yml) failed.

Run: https://github.com/tuna-os/tunaOS/actions/runs/43015859855 (attempt 1)
Commit: cdaec35e8bed0a8c00fe66115c535c88950bb49a

Failed jobs:

🤖-gurnard / pantheon / linux-arm64
🤖-gurnard / pantheon / linux-amd64
🤖-gurnard / pantheon / Manifest
🤖-gurnard / iso:pantheon (linux-amd64) / ISO gurnard:pantheon
🤖-gurnard / iso:pantheon (linux-arm64) / ISO gurnard:pantheon

Filed by .github/workflows/scheduled-failure-alert.yml. Later failures of this workflow comment here; the next green scheduled run closes the issue.

github-actions
added
ci-failureCreated by Hive for agent-filed issue provenance
on Nov 11, 2026
hanthor-hive-agent
added
stage/010-actionableTriaged; eligible for the hive to pick up
on Nov 11, 2026
github-actions commented on Nov 11, 2026
github-actionsBot
on Nov 11, 2026 – with GitHub Actions
ContributorAuthor
Failed again: https://github.com/tuna-os/tunaOS/actions/runs/43015859855 (attempt 2)

Failed jobs:

🤖-gurnard / pantheon / linux-arm64

🤖-gurnard / pantheon / linux-amd64

🤖-gurnard / pantheon / Manifest

🤖-gurnard / iso:pantheon (linux-amd64) / ISO gurnard:pantheon

🤖-gurnard / iso:pantheon (linux-arm64) / ISO gurnard:pantheon

to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

Labels

ci-failurestage/010-actionable

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests