container-canary CI check is flaky: "unexpected commit digest"
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 87
- Forks
- 59
- Avg merge
- 22h 56m
- Merged PRs (30d)
- 4
Description
Description
Over the last few days, I've observed the validate jobs in CI often failing like this:
failed commit on ref "layer-sha256:2609f790a90ab5307cbbb99bd5de7e5912f440c225ffbf91122d212f48a1dfcf": commit failed: unexpected commit digest sha256:c3728131ea5aa7dddea03141cea9af41b08c03c2a6a6a0fdca0b37d13341f1f5, expected sha256:2609f790a90ab5307cbbb99bd5de7e5912f440c225ffbf91122d212f48a1dfcf: failed precondition
This is always resolved with 1 or 2 re-runs. There's something flaky about those jobs.
Benefits of this work
Fixing this would reduce the manual effort needed to merge PRs and keep nightly workflows running successfully.
Acceptance Criteria
Nightlies succeed for 2 consecutive days with no failures in the validate jobs.
Approach
N/A
Notes
N/A
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the validate jobs in the linked nightly GitHub Actions run and the repository's nightly workflow definitions. Investigate why the reported commit digest differs from the expected layer digest and reproduce the failure if possible. Done means nightlies complete for two consecutive days without validate-job failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, shell
- Domain
- build-system, ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100