Mark chisel tests as flaky
Metadata
Current evaluation
Closed without implementation. The enhancement to retry flaky chisel tests via pytest-rerunfailures was not applied.
Suggested action: —
No scores available.
Issue body
### What needs to get done
The integration tests for chisel are dependent on perfect network connections between the device and `archive.ubuntu.com`, which isn't reasonable.
https://github.com/pytest-dev/pytest-rerunfailures
### Why it needs to get done
We should allow them to be retried at least once before failing in order to avoid re-running the entire workflow just because those tests failed.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The enhancement to retry flaky chisel tests via pytest-rerunfailures was not applied. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The enhancement to retry flaky chisel tests using pytest-rerunfailures was logged but not merged, likely abandoned or superseded. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. A Jira ticket was created to track the enhancement for retrying flaky chisel tests, but no code changes or PRs were merged. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The enhancement to retry flaky chisel integration tests was superseded by an internal Jira ticket. No code changes or pull requests were merged. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1308 fix(test): mark chisel integration tests as flaky | craft-parts | merged | Merged changes marking chisel integration tests as flaky to accommodate intermittent network failures. Approved by two reviewers, passed CI checks, and resolves issue #1306. |