Closed sunchao closed 2 months ago
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: No coverage uploaded for pull request base (
main@72398a6
). Click here to learn what that means.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
❗ No coverage uploaded for pull request base (main@72398a6).
@sunchao you may need to rebase the latest main to compare coverage difference.
@sunchao you may need to rebase the latest main to compare coverage difference.
Oh thanks for letting me know. I'll address the test failures first, and then do the rebasing.
cc @viirya @advancedxy @kazuyukitanimura this is ready for review now.
I'll create a separate Github issue to track the work of creating a branch for the diff changes.
I applied the diff change to my own fork of Spark 3.4.2 here to make it easier to review.
I left some comments on this and https://github.com/sunchao/spark/commit/f7c15aa4a9c0462f17a8994102a1c707b07629d6. LGTM generally.
@advancedxy there are still some issues when enabling shuffle in Spark SQL tests. I'll address them separately later in a follow-up. Let me know what you think of the latest change.
(the CI failure is unrelated)
I'll address them separately later in a follow-up. Let me know what you think of the latest change.
That sounds good to me. I took anther look, only one minor comment, LGTM otherwise.
Thanks, merged
Which issue does this PR close?
Closes #8.
Rationale for this change
We want to leverage SQL tests in Spark itself to increase our test coverage. We should run them with Comet enabled and make sure the tests pass all the existing checks.
What changes are included in this PR?
This PR enables us to run SQL tests in Spark itself in Comet. To enable Comet for Spark, a diff file is introduced to patch Spark (version 3.4.2) so that we can:
ENABLE_COMET
)How are these changes tested?