[SPARK-54889][INFRA] Report test results to codecov #53665
Closed
+18
−2
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
JIRA Issue Information=== Test SPARK-54889 === This comment was automatically generated by GitHub Actions |
gaogaotiantian
changed the title
zhengruifeng
approved these changes
Jan 5, 2026
Contributor
|
thanks, merged to master |
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.
What changes were proposed in this pull request?
Upload test reports to Codecov.io for all main commits to have a nice dashboard to check test flakyness and performance.
Why are the changes needed?
Currently we have no insights into our tests. We don't know if a test is flaky, when a test has been failing or how long a test takes.
Codecov is a free solution and we are using it for coverage report already. It will produce something like
and it's much much better than nothing.
Does this PR introduce any user-facing change?
No
How was this patch tested?
I tried to enable it on PR and generated the dashboard above on my own repo. The syntax should be correct but we only want data from master for now.
Was this patch authored or co-authored using generative AI tooling?
No