mvnd IT: increase connectTimeout for ITs #1171
Merged
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
Just a desperate PR to figure out why MacOS GH runners keep failing with transport related (SSL handshake abort, HTTP timeouts) errors.
cstamas
changed the title
This reverts commit 826af6b.
Circumvent low connectTimeouts and GH macOS runners when JDK transport is used (default).
cstamas
changed the title
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.
Experiment PR to figure out why MacOS GH runners keep failing with transport related (SSL handshake abort, HTTP timeouts) errors. As we know linux and windows boxes are in Azure, while macos boxes are somewhere else, and we get regularly real strange errors like "SSL handshake errors", "HTTP timeout error (against Central?)", so suspicion is on JDK transport (in HTTP/2 mode).
Experiments:
Conclusion: apache transport ignores "request timeout" seemingly, so it performs "more robust", while JDK transport strictly enforces timeouts, and it seems GH macOS runners are having way slower networking. For ITs we will for now increase the default (10sec)
connectTimeoutResolver configuration, as it seems too low.