Repository navigation
[WIP][DO-NOT-MERGE] bisect: old-harness pytest cwd/abs-path (arrow-udf hang) - #70
Closed
HyukjinKwon wants to merge 1 commit into
Closed
HyukjinKwon wants to merge 1 commit into
HyukjinKwon wants to merge 1 commit into
Conversation
…(SPARK-58987 arrow-udf hang) Co-authored-by: Isaac <no-reply@databricks.com>
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
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.
Sub-bisection of the parity-harness regression. Off the full commit 6ca3ebd, changes ONLY run_ours() to invoke pytest the way the old harness did (absolute file path, repo-root cwd, no cwd=/python). If test_parity_arrow_python_udf.py returns to ~315 passed, the new runner's cwd/rootdir/conftest context is the cause of the p=0 setup hang. Not for merge.