[SPARK-55346][INFRA][PYTHON] Upgrade pystack version to 1.6.0 and install it on all major images#54124
Closed
gaogaotiantian wants to merge 1 commit intoapache:masterfrom
Closed
[SPARK-55346][INFRA][PYTHON] Upgrade pystack version to 1.6.0 and install it on all major images#54124gaogaotiantian wants to merge 1 commit intoapache:masterfrom
gaogaotiantian wants to merge 1 commit intoapache:masterfrom
Conversation
JIRA Issue Information=== Improvement SPARK-55346 === This comment was automatically generated by GitHub Actions |
HyukjinKwon
approved these changes
Feb 4, 2026
Member
|
Merged to master. |
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?
Why are the changes needed?
pystack used to lack 3.13t wheels and we had to skip 3.13 for requirements. Now it supports it so we don't need this special rule.
pystackhas been proven very useful to find hanging issues (#53783). Enabling it on not only master, but also other scheduled tests could help us diagnosis more hanging issues (notice that master is using 3.12 now so we are not even using it on master).For example, https://github.com/apache/spark/actions/runs/21645825351/job/62398366525 is a hanging issue but we have no information from it.
https://github.com/apache/spark/actions/runs/21648052684/job/62405320893 also timed out without useful information.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
It has been working well with 3.11 without causing issues. It helped us figure out a very difficult racing issue.
Was this patch authored or co-authored using generative AI tooling?
No.