Generate test report per JDK version for easier triage #18817
Merged
+7
−3
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
Currently we use one uber test-report across both JDK versions 17 and 21. Some tests may be flaky or even have JDK specific errors that can make it slightly difficult to identify the source of the error. So this patch should help which JDK/job to look into in case of errors rather than having to hunt down between the different versions.
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.
Currently, we generate a single consolidated test-report across both JDK 17 and JDK 21. Some tests may fail or flake only on one JDK version, which makes it harder to identify the source of the error.
This patch generates a separate test report per JDK version, which will allow us to identify the source of a failure by checking the corresponding JDK-specific job. An example of such a test report can be seen here on my fork.
These test-report jobs typically take about a minute to complete, so splitting it per JDK version shouldn't add additional overhead.