doc(coverage): the HA gap is closed, so say so in the past tense - #48
Merged
Conversation
#47 merged between this branch being written and being merged. CI no longer runs a standalone mongo, so the section that described the gap now describes how it was closed - the mongo-rs service image in the three jobs that run the suite, and why the perf and ETSI jobs deliberately keep a standalone. The numbers above it are untouched: they were measured against a replica set in the first place, which is how the discrepancy was noticed at all. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TGatXwrHx1CreL49sCuS37
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.
Follow-up to #47, which closed the gap that #46's HA section described as live.
doc/coverage.mdnow says how the gap was closed — themongo-rsservice image in the three jobs that run the suite, and.github/scripts/mongo-rs-init.sh— and records why the perf and ETSI jobs deliberately keep a standalone, so nobody "fixes" the perf job and moves its baseline out from under it.The measured numbers above that section are untouched. They were taken against a replica set in the first place, which is how the discrepancy was noticed at all.
The section keeps its point, which outlives this particular bug: a coverage figure measures an environment as much as it measures a suite, and nothing in the output tells you which environment produced it.
🤖 Generated with Claude Code
https://claude.ai/code/session_01TGatXwrHx1CreL49sCuS37