CI failure debugging - Dump Quarkus process launch logs if JarRunnerIT fails with condition timeout exceptions #9960
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
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.
JarRunnerIT test case (the "fast jar" test methods) is consistenly failing on CI jobs with condition timeout exceptions. However, it passes locally. The CI jobs don't have any hints on what's going wrong (and why a timeout of 1 minute isn't enough to launch the Quarkus process in that test).
The commit in this PR, is one attempt to try and see what's really going on. This change doesn't fix the failures but will dump the logs of the Quarkus process launch, if (and only if) a condition timeout occurs in that test. This might give us a clue if it really is taking more than a minute to launch it and if yes then why. We might need more debugging logs in that test case, but before I go do extensive changes in there, I wanted to see if this simple attempt will show up what's going on there.