Fix frequent CI failures of MDCReactorSpec #10031
Merged
+8
−1
Conversation
This file contains 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
This sets the read timeout of the main http client (which is manually instantiated) used in MDCReactorSpec to 5 minutes, which is the same as what is set for the dependency-injected clients used elsewhere throughout the test. This spec was frequently failing in CI with an HTTP read timeout error, likely due to resource starvation on the CI job runner causing slow responses from the embedded server that is used in the test.
|
Kudos, SonarCloud Quality Gate passed!
|
sdelamo
approved these changes
Oct 26, 2023
Open
1 task
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.
This sets the read timeout of the main http client (which is manually instantiated) used in MDCReactorSpec to 5
minutes, which is the same as what is set for the dependency-injected clients used elsewhere throughout the test.
This spec was frequently failing in CI with an HTTP read timeout error, likely due to resource starvation on the CI
job runner causing slow responses from the embedded server that is used in the test.
This should fix #10026