[Python][CI] Configure warnings as errors during build/test #36642
Comments
danepitkin
changed the title
danepitkin
added a commit
to danepitkin/arrow
that referenced
this issue
Aug 3, 2023
kou
pushed a commit
that referenced
this issue
Aug 7, 2023
…7018) ### 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: #36642 Authored-by: Dane Pitkin <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
loicalleyne
pushed a commit
to loicalleyne/arrow
that referenced
this issue
Nov 13, 2023
…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]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the enhancement requested
Warnings are continuously being introduced into the pyarrow tests. Let's enforce warnings as errors in at least one CI build (probably one that covers latest versions of python/dependencies).
Component(s)
Python
The text was updated successfully, but these errors were encountered: