Repository navigation
test: the smoke test bounds its wait for Mongo and names why it failed - #13
Merged
Merged
Conversation
Since 09:03 on 2026-10-21 every CI run, main's included, has hung in the unbounded wait for Mongo's replica set until the job's 30-minute timeout cancelled it. The wait now gives up after two minutes, says whether Mongo exited or never became a replica set, and prints its log. It matches the whole output line, so an error naming 127.0.0.1 no longer passes as ok.
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.
Every CI run since 09:03 UTC on 2026-10-21, main's included, hung in the smoke test's unbounded wait for Mongo's replica set until the 30-minute job timeout cancelled it. That blocked #12.
The wait now gives up after two minutes, and says whether Mongo exited or never became a replica set, printing Mongo's log. It also matches the whole output line, so an error naming
127.0.0.1no longer passes as ok.Checks
This branch's smoke test passes, with Mongo up as a replica set within the bound. The hang did not reproduce, so its cause is unconfirmed:
mongo:8.0has been 8.0.34 since 2026-10-17, and both arm64 and amd64 (emulated) form the replica set locally. If it comes back, the job now fails in two minutes with Mongo's log instead of hanging.