chore(ci): Disable testcontainers ryuk reaper in integration tests - #19604
Merged
skartikey merged 1 commit intoSep 1, 2026
Merged
Conversation
srebhan
approved these changes
Sep 1, 2026
srebhan
left a comment
Member
There was a problem hiding this comment.
Awesome finding @skartikey! 🚀
Contributor
|
Download PR build artifacts for linux_amd64.tar.gz, darwin_arm64.tar.gz, and windows_amd64.zip. 📦 Click here to get additional PR build artifactsArtifact URLs |
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
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
The test-integration job fails a few times a week with a single test dying on
reaper: from container "xxxx": wait for reaper xxxx: context deadline exceeded(recently alwaysTestIntegrationArtemisin jolokia2_agent, e.g. jobs 551595, 551618, 551879, 551886, 551994, 552040). All test package processes of onego test ./...invocation share a single ryuk container, and ryuk exits 10 seconds after the last test process disconnects. In a full./...run there are natural gaps with no active container tests, so ryuk legitimately dies mid-run; the next package that needs a container then finds the dead ryuk container (testcontainers-go looks it up withAll: trueand no running-state filter) and spends 60 seconds waiting for it to become ready before failing. The same package keeps getting hit because package scheduling on the fixed runner is roughly deterministic.Ryuk only exists to clean up leaked containers, and the job runs on an ephemeral CircleCI machine VM that is destroyed after the job, so it provides no value here. Disabling it removes the whole reaper code path and with it this failure mode.
Checklist
Related issues
resolves #19605