Improve flaky test reporting #13477
Merged
Improve flaky test reporting #13477
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
jaydeluca
reviewed
Mar 8, 2025
test-report/src/main/java/io/opentelemetry/instrumentation/testreport/FlakyTestReporter.java
Show resolved
Hide resolved
jaydeluca
approved these changes
Mar 9, 2025
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.
Apparently recently the timestamp in junit test reports contain a time zone like in
2025-03-08T05:04:57.500ZGoogle sheets doesn't seem to be able to automatically parse this as a data. To overcome this we'll strip the time zone.This PR also adds detection for when test report is restored from gradle build cache and ignores flaky tests for these.