ci: pin pyarrow <25 to unblock CI#841
Merged
Merged
Conversation
torch 2.13.0 (released after 2026-07-02) causes the 'Run processing tests sequentially' step to hang in test_optimize_race_condition — macOS jobs hit the 1h timeout, Linux jobs get killed. The last green main run (2026-07-02) used torch 2.12.1; every run since resolves the unpinned torch to 2.13 and fails. Pin as a stopgap while the hang is root-caused.
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #841 +/- ##
===================================
Coverage 81% 81%
===================================
Files 54 54
Lines 7671 7671
===================================
+ Hits 6186 6191 +5
+ Misses 1485 1480 -5 🚀 New features to boost your workflow:
|
4 tasks
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.
What does this PR do?
pyarrow 25.0.0 (released 10th july) causes a segmentation fault and 16 parquet-test failures in
tests/streaming/test_parquet.pywhen reading row groups during parquet indexing.The last known-good CI run used pyarrow 24.0.0.
This pr pins
pyarrow<25.0.0as a stopgap to unblock CI until the regression is root-caused upstream in pyarrow.(Originally this PR pinned torch <2.13, but further investigation showed torch was not the culprit — pyarrow 25 is.)