Publish coverage from one matrix leg - #187
Merged
Merged
Conversation
`coveralls --service=github` derives its job id from GITHUB_RUN_ID, which is the same for all five matrix legs. Five submissions claim the same job for the same commit, Coveralls accepts one and 422s the rest, and the step's non-zero exit fails the build -- intermittently, whichever leg loses the race (PR #185, 3.11). Coverage is identical across interpreter versions, so publishing from 3.12 alone loses nothing and removes the collision. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Bucknalla
approved these changes
Sep 23, 2026
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
2 participants
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.
coveralls --service=githubderives its job id fromGITHUB_RUN_ID, which is identicalacross all five matrix legs. Five submissions claim the same job for the same commit,
Coveralls accepts one and 422s the rest, and the non-zero exit fails the build.
Seen on #185:
All 419 tests had passed; only the publish step failed. It's a race, so it bites
intermittently — whichever leg loses.
Coverage is identical across interpreter versions, so publishing from 3.12 alone
removes the collision and loses nothing.
🤖 Generated with Claude Code