[SPARK-53728][SDP] Print PipelineEvent Message with Error In Test #52463
+39
−16
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
JiaqiWang18
force-pushed
the
SPARK-53728-print-event-with-error-in-test
branch
from
646df20 to
21f5755
Compare
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.
What changes were proposed in this pull request?
Pulling some changes from #51644
For debugging purposes, print PipelineEvent with error to the console. Most tests expects pipeline to succeed, this makes it easier to see the error when it happens. Otherwise, developers have to manually add println to print the error message contained in the event, which is cumbersome.
Why are the changes needed?
Easier to debug test failures, avoid the need to manually add println for test failures.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?
No