ci(rust-ci): bump reusable pin to 822fa14e (estate-wide 0s parse failure)#92
Closed
hyperpolymath wants to merge 1 commit into
Closed
ci(rust-ci): bump reusable pin to 822fa14e (estate-wide 0s parse failure)#92hyperpolymath wants to merge 1 commit into
hyperpolymath wants to merge 1 commit into
Conversation
…rse failure) panic-attack rust-ci.yml + 42 other estate repos that pin rust-ci-reusable.yml@cc5a372a have been failing with 0s-duration "workflow file issue" parse errors since 2026-05-26 (when PR #45 introduced the thin-wrapper). cc5a372a IS reachable from standards/main (verified via git merge-base --is-ancestor), so this is NOT the orphan-SHA failure mode panic-attack#84 thought it was fixing. Empirical: every recent rust-ci run failed at parse time. The reusable's content at cc5a372a is structurally fine. The simplest hypothesis is that GH Actions has cached a bad resolution of this specific SHA — repinning to a fresher merge-commit forces re-fetch. 822fa14e is the current HEAD of standards/main on the file (standards#299, "pass --locked to cargo check/clippy/test"). Bumping forward to that brings the --locked safety along with the unblock. If 822fa14e also fails parse: the issue is not the SHA, and the caller-side workflow file needs investigation (the workflow's API-reported name field has been ".github/workflows/rust-ci.yml" not "Rust CI", suggesting GH never parsed it successfully). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Owner
Author
|
Closing — SHA bump alone doesn't fix it. Latest run on this branch (2026-05-30T23:24:11Z, after 822fa14e pin) still produces a 0s 'completed failure' with no log/jobs. The workflow API also still reports the workflow's name as the path ( |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
`rust-ci.yml` has been failing on every push to main since 2026-05-26
with 0s-duration "workflow file issue" parse errors. This affects 43+
estate repos all pinning the same SHA.
panic-attack#84 ("repin orphan reusable SHAs") tried to fix this by
swapping the old pin `4fdf4314` for `cc5a372a`. But `cc5a372a`
is verifiably reachable from standards/main:
```
$ git merge-base --is-ancestor cc5a372a HEAD && echo REACHABLE
REACHABLE
```
So the cause is NOT orphan SHA. The diff between cc5a372a and current
main HEAD on `rust-ci-reusable.yml` is just SPDX header + `--locked`
addition — no parse-breaking semantic change.
Empirical fix attempt: bump to `822fa14e` (current standards/main HEAD)
to force GH Actions to re-resolve the workflow file, on the hypothesis
that GH has cached a bad resolution for `cc5a372a`. Side benefit: picks
up the `--locked` safety flag from standards#299.
Test plan
If 822fa14e ALSO fails parse, the issue is upstream (caller workflow
structure, GH Actions parser quirk) and needs deeper investigation —
the workflow's API name field is ".github/workflows/rust-ci.yml" not
"Rust CI", strongly suggesting it has never been successfully parsed
since some recent change.
🤖 Generated with Claude Code