[CloudTest] Restart emulator process if the initial setup requests fail #40
Conversation
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
Member
|
Mind taking a look at the nightly failure? I restarted the test and it reproduced a 2nd time; my hunch is it's not related specifically to your changes here, but this is the first time we're seeing nightly start to fail like this. ref: https://github.com/JuliaServices/CloudBase.jl/actions/runs/19711239168/job/56654416779?pr=40 |
quinnj
approved these changes
Nov 28, 2025
Collaborator
Author
|
@quinnj Thank you for the review. The nightly failure is unrelated and was already present on the latest merged PR. Will merge this one. |
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.
We are encountering an issue where the emulator process (Azurite/MinIO) starts and the TCP port opens but the emulator is in a bad state and the initial requests fail persistently with IO errors causing the tests that depend on them to fail spuriously. All instances that we have observed have succeeded upon retry with a fresh emulator process so this PR adds the process restart retry logic to CloudTest itself to prevent flakiness downstream.