docs: F7 covers both CI flakes; second one ties to F10 - #165
Merged
Conversation
A second flake surfaced while merging #164, a docs-only change: Docker Hub reset the connection pulling postgres:15 for the testcontainer. A rerun passed. That is a different failure mode from the NATS race already recorded -- an external dependency rather than a race -- so F7 now documents both and is retitled accordingly. Two of the nine tests that actually execute in CI are therefore unreliable, roughly a 22% false-failure rate on the entire signal. Both were observed on docs-only PRs in one afternoon, so neither could have been caused by the change under review. The image-pull flake connects to F10: platform's CI is coupled to third-party uptime through live API calls, ours through container image pulls. Same exposure, different door, and neither repo defends against it -- no retry, no registry mirror, no pre-pull. Noted that any fix for F1 which adds containers widens this surface rather than narrowing it: the SLURM cluster in A4 pulls about 2.8 GB, so a mirror or pull-retry belongs inside that work. Group E gains the image-pull decision alongside the race fix. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018TgVbCXXWAWhNjtKTzrxvN
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
A second flake surfaced while merging #164 — itself a docs-only change — so F7 is no longer accurate as written.
The new one is a different failure mode. Docker Hub reset the connection while pulling
postgres:15for the testcontainer:A rerun passed. Nothing in the repo is at fault, and nothing in the repo defends against it either: no retry, no registry mirror, no pre-pull step.
What changed
platform's CI is coupled to third-party uptime through live API calls; ours through container image pulls. Same exposure, different door. Worth noting that any fix for F1 which adds containers widens this surface — the SLURM cluster in A4 pulls ~2.8 GB — so a mirror or pull-retry belongs inside that work rather than after it.Checked that no stale "single flaky test" or "eleven percent" wording survives elsewhere.
make checkclean;mkdocs build -spasses.🤖 Generated with Claude Code
https://claude.ai/code/session_018TgVbCXXWAWhNjtKTzrxvN