Retry publish to edge action
Metadata
Current evaluation
Retry request was deferred to canonical/craft-actions#48; proposed Snapcraft PR #5989 (4cff0d0) was closed unmerged.
Resolution: closed superseded
Reason: Maintainer mr-cal deferred the retry implementation to canonical/craft-actions#48. PR #5989 and commit 4cff0d0 were not merged into Snapcraft.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### Check existing issues
- [x] I've verified that this request isn't described by any existing issues.
### Request
The last step in the https://github.com/canonical/snapcraft/blob/main/.github/workflows/publish.yaml action sometimes fails with:
```bash
('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
```
If this happens, we should wait 60 seconds and retry once. Keep it simple - the timeout and number of retries doesn't need to be configurable.
### The problem it solves
To improve flakiness of the CI suite.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed superseded | Retry request was deferred to canonical/craft-actions#48; proposed Snapcraft PR #5989 (4cff0d0) was closed unmerged. | |
| stealth/space-bunny-alpha | — | closed superseded | Retry was deferred to canonical/craft-actions#48; PR #5989 (commit 4cff0d0) was closed unmerged, so no Snapcraft-side retry landed. | |
| stealth/space-bunny-alpha | — | closed superseded | Deferred to canonical/craft-actions#48: PR #5989 was closed unmerged, and its retry implementation (4cff0d0) was not landed; the edge-publish retry request was closed. | |
| stealth/space-bunny-alpha | — | closed superseded | Publish-edge retries were deferred: PR #5989 was rejected, and the request was closed pending the shared publish action in canonical/craft-actions#48. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed as superseded. The requested retry mechanism for the flaky publish action depends on an upstream fix in canonical/craft-actions#48 and remains deferred until that PR is resolved. | |
| qwen/qwen3.6-35b-a3b | — | — | Superseded pending upstream resolution. The maintainer deferred local retry logic, awaiting canonical/craft-actions#48 to resolve the publish action flakiness. | |
| qwen/qwen3.6-35b-a3b | — | — | Superseded by upstream work in canonical/craft-actions#48. The maintainer closed the CI retry request, noting the implementation was complex and waiting for the upstream dependency to resolve the connection abort issue. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Deferred pending upstream fix in canonical/craft-actions#48. The maintainer noted the local retry is non-trivial and better addressed by an upstream action update to resolve CI publish flakiness. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/snapcraft#5989
(confidence 100%)
Proposed Snapcraft-side retry handling in commit 4cff0d0, but the PR was closed unmerged.
-
Superseded By:
canonical/craft-actions#48
(confidence 98%)
The maintainer explicitly identified this shared-action work as the place to implement publish retries.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #5989 Add retry logic to publish action for connection failures | snapcraft | closed | Copilot PR #5989 (commit 4cff0d0) added retry-on-connection-error logic to publish.yaml but was closed unmerged; mr-cal deferred the work to canonical/craft-actions#48, still open. | |
| #48 "Publish snap" action | craft-actions | open | Maintainer-filed, triaged enhancement asking for a `snapcraft/publish` action wrapping `snapcraft upload --release`, working with `snapcraft/pack`; still unimplemented, with a follow-up request for retry on store connection errors. |