Skip to content

Conversation

@SCHJonathan
Copy link
Contributor

What changes were proposed in this pull request?

In #53024 (comment), PR CI Python unit tests failed due to

pyspark.errors.exceptions.base.PySparkImportError: [PACKAGE_NOT_INSTALLED] zstandard >= 0.25.0 must be installed; however, it was not found.

This PR add the required dependency to the pre-merge CI.

Why are the changes needed?

Recover Python unit tests CI

Does this PR introduce any user-facing change?

No

How was this patch tested?

PR #53024 Python CI back to healthy with this change

Was this patch authored or co-authored using generative AI tooling?

No

@zhengruifeng zhengruifeng changed the title [SPARK-54348] Recover Python unit tests CI by installing zstandard==0.25.0 [SPARK-54348][INFRA] Recover Python unit tests CI by installing zstandard==0.25.0 Nov 14, 2025
@LuciferYang
Copy link
Contributor

@SCHJonathan Which Scala-side test cases will be affected by zstandard? We should also add some assume statements for these cases to ensure that they are skipped rather than failing when zstandard is not available.

@dongjoon-hyun
Copy link
Member

To @sryza , the absolute path patch seems to break our CI on this PR somehow.

[info] EndToEndAPISuite:
[info] - SQL Pipeline with mv, st, and flows *** FAILED *** (690 milliseconds)
[info]   java.lang.RuntimeException: Pipeline update process failed with exit code 1.
...
[info] pyspark.errors.exceptions.connect.SparkException: [PIPELINE_STORAGE_ROOT_INVALID] Pipeline storage root must be an absolute path with a URI scheme (e.g., file://, s3a://, hdfs://). Got: `/home/runner/work/spark/spark/target/tmp/spark-e693e257-1d24-4b6f-9265-2510010e5366/storage`. SQLSTATE: 42K03

@dongjoon-hyun
Copy link
Member

dongjoon-hyun commented Nov 14, 2025

@dongjoon-hyun
Copy link
Member

Could you re-trigger the failed test pipeline, please, @SCHJonathan ?

@sryza
Copy link
Contributor

sryza commented Nov 14, 2025

Here's a PR to fix the EndToEndAPITest test failure: #53069. It fails reliably, I think it just must have somehow been skipped in the CI for my original PR.

@SCHJonathan
Copy link
Contributor Author

To @sryza , the absolute path patch seems to break our CI on this PR somehow.

Thanks @dongjoon-hyun , for this test, I have fixed it in #53024. I just re-trigger and the other failing test pipeline

@SCHJonathan
Copy link
Contributor Author

@SCHJonathan Which Scala-side test cases will be affected by zstandard? We should also add some assume statements for these cases to ensure that they are skipped rather than failing when zstandard is not available.

In this case, it is the org.apache.spark.sql.connect.pipelines.PythonPipelineSuite

@dongjoon-hyun
Copy link
Member

Copy link
Member

@dongjoon-hyun dongjoon-hyun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, LGTM. Thank you, @SCHJonathan and @sryza .
Merged to master/4.1.

dongjoon-hyun pushed a commit that referenced this pull request Nov 14, 2025
…ndard==0.25.0`

### What changes were proposed in this pull request?

In #53024 (comment), PR CI Python unit tests failed due to
```
pyspark.errors.exceptions.base.PySparkImportError: [PACKAGE_NOT_INSTALLED] zstandard >= 0.25.0 must be installed; however, it was not found.
```
This PR add the required dependency to the pre-merge CI.

### Why are the changes needed?

Recover Python unit tests CI

### Does this PR introduce _any_ user-facing change?

No

### How was this patch tested?

PR #53024 Python CI back to healthy with this change

### Was this patch authored or co-authored using generative AI tooling?

No

Closes #53058 from SCHJonathan/jonathan-chang_data/fix-python-ci-dep.

Authored-by: Yuheng Chang <[email protected]>
Signed-off-by: Dongjoon Hyun <[email protected]>
(cherry picked from commit a916690)
Signed-off-by: Dongjoon Hyun <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants