Flaky test: TestContainerRestartPolicyUserDefinedNetwork
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 72.1k
- Forks
- 19.2k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 164
Description
Description
TestContainerRestartPolicyUserDefinedNetwork (in integration/container/restart_test.go) failed intermittently in CI during the 2026-09-09 to 2026-09-12 scan window.
Failure evidence:
| Run | Branch | Job | Result |
|---|---|---|---|
| 34475195808 | trixie_me_trixie_you |
vm (template:oraclelinux-8, ...) / integration |
❌ FAIL (12.20s) |
| 34475195808 | trixie_me_trixie_you |
vm (template:oraclelinux-8, ...) / integration (rootless) |
❌ FAIL (12.27s) |
Passing evidence (same 72h window, independent master runs):
| Run | Branch | Job | Result |
|---|---|---|---|
| 34598138516 | master |
vm / integration |
✅ PASS (3.44s) |
| 34598138516 | master |
vm / integration (rootless) |
✅ PASS (3.22s) |
| 34508344173 | master |
vm / integration |
✅ PASS (3.48s) |
| 34508344173 | master |
vm / integration (rootless) |
✅ PASS (3.17s) |
Classification: Flaky — the test consistently passes (~3s) on master across multiple independent runs in the same window, but failed (~12s, ~4x the normal duration) on the trixie_me_trixie_you experimental/WIP branch, both in the rootless and non-rootless job variants of the same run. The longer duration before failure suggests a timing/readiness race (e.g. waiting for the user-defined network or container restart to settle) rather than a deterministic logic bug, consistent with typical restart-policy test flakiness in this package (see also #52551).
No existing tracking issue was found for this specific test via search of moby/moby issues (open or closed) or the flaky-tests epic (#37306, closed).
cc @vvoland
Flagged by automated CI flakiness scan.
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 in integration/container/restart_test.go with TestContainerRestartPolicyUserDefinedNetwork and compare its behavior in the cited passing and failing CI runs. Read the related flakiness discussion in #52551 and investigate the restart or user-defined-network readiness timing; done means the test is reliable in both rootless and non-rootless integration jobs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100