[SPARK-55858][PYTHON][INFRA] Fix UDF logging tests under coverage#54649
Open
gaogaotiantian wants to merge 1 commit intoapache:masterfrom
Open
[SPARK-55858][PYTHON][INFRA] Fix UDF logging tests under coverage#54649gaogaotiantian wants to merge 1 commit intoapache:masterfrom
gaogaotiantian wants to merge 1 commit intoapache:masterfrom
Conversation
HyukjinKwon
approved these changes
Mar 6, 2026
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
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?
When we patch workers with coverage, pretend the
sitecustomizemodule that coverage uses to be the worker module.Why are the changes needed?
UDF logging uses module name to determine whether the code is user code. With coverage, we have a strange module
sitecustomizeand UDF logging believes it's user code - which breaks the test.We should not modify our production code to make coverage work, so we patch the coverage code.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Locally the failed test passed.
Was this patch authored or co-authored using generative AI tooling?
No.