-
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-36642: [Python][CI] Configure warnings as errors during pytest #37018
Conversation
Thanks for opening a pull request! If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project. Then could you also rename the pull request title in the following format?
or
In the case of PARQUET issues on JIRA the title also supports:
See also: |
I enabled warnings as errors for conda python 3.8 through 3.11 and for conda python pandas integration to see what happens. Realistically, we probably want to limit warnings to just the latest python version (currently 3.11). |
@github-actions crossbow submit test-conda-python* |
Revision: 9195826 Submitted crossbow builds: ursacomputing/crossbow @ actions-1e510b906c |
For python 3.8 through 3.11 there is only 1 warning (repeated in 5 test cases).
|
@github-actions crossbow submit test-conda-python* |
Revision: 6db95f6 Submitted crossbow builds: ursacomputing/crossbow @ actions-2a9b540c67 |
@github-actions crossbow submit test-conda-python* |
Revision: fca7663 Submitted crossbow builds: ursacomputing/crossbow @ actions-45800058d0 |
|
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
BTW, are you interested in taking over #36745 from me...?
Hey @kou, sure I can take a look! |
Thanks! |
After merging your PR, Conbench analyzed the 5 benchmarking runs that have been run so far on merge-commit 2b36521. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about possible false positives for unstable benchmarks that are known to sometimes produce them. |
…st (apache#37018) ### Rationale for this change Warnings are constantly being introduced into the pyarrow tests. Let's try enforcing them as errors in an effort to keep the codebase healthy. ### What changes are included in this PR? * Fixed existing warnings * Set warnings as errors in CI ### Are these changes tested? Yes, ran pytests locally w/o warnings. ### Are there any user-facing changes? No * Closes: apache#36642 Authored-by: Dane Pitkin <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
Rationale for this change
Warnings are constantly being introduced into the pyarrow tests. Let's try enforcing them as errors in an effort to keep the codebase healthy.
What changes are included in this PR?
Are these changes tested?
Yes, ran pytests locally w/o warnings.
Are there any user-facing changes?
No