-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GH-44369: [CI][Python] Remove ds requirement from test collection on test_dataset.py #44370
Conversation
…on on test_dataset.py
|
@github-actions crossbow submit example-python-minimal-build-* |
Revision: d682c4f Submitted crossbow builds: ursacomputing/crossbow @ actions-b410c377ee
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing this!
After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit e0d1f51. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 1 possible false positive for unstable benchmarks that are known to sometimes produce them. |
…test_dataset.py (#44370) ### Rationale for this change If pyarrow has been built without dataset test collection errors due to pytest.mark.parametrize requiring dataset. ### What changes are included in this PR? Move dataset requirement outside of test collection by removing it from the parametrization. ### Are these changes tested? Via archery ### Are there any user-facing changes? No * GitHub Issue: #44369 Authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
Rationale for this change
If pyarrow has been built without dataset test collection errors due to pytest.mark.parametrize requiring dataset.
What changes are included in this PR?
Move dataset requirement outside of test collection by removing it from the parametrization.
Are these changes tested?
Via archery
Are there any user-facing changes?
No