Skip to content

CI: Fail on warning for 3.9 #34852

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

Closed
wants to merge 3 commits into from

Conversation

TomAugspurger
Copy link
Contributor

This should fail till #34835 is in.

@jreback jreback added the CI Continuous Integration label Jun 17, 2020
@jreback jreback added this to the 1.1 milestone Jun 17, 2020
.travis.yml Outdated
@@ -33,7 +33,7 @@ matrix:
- dist: bionic
python: 3.9-dev
env:
- JOB="3.9-dev" PATTERN="(not slow and not network and not clipboard)"
- JOB="3.9-dev" PATTERN="(not slow and not network and not clipboard)" TEST_ARGS="-Werror"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This gets passed to pytest right? I think the flag there is just -W

https://docs.pytest.org/en/latest/warnings.html

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or could even do in the setup.cfg

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Trying it out in setup.cfg. The primary issue I see is that we don't necessarily want warnings from optional dependencies to cause errors. For now I've limited to just our required dependencies.

@WillAyd
Copy link
Member

WillAyd commented Jun 18, 2020

Just out of curiosity what are you trying to do specific to 3.9? I think great to do this, though obviously would require a good deal of work to get it to work across all builds

@TomAugspurger
Copy link
Contributor Author

Just out of curiosity what are you trying to do specific to 3.9?

The 3.9 job builds NumPy from source, and so it can be slightly ahead of the numpydev build (our only other build to error on warnings) which uses NumPy's nightly wheels.

Agreed this would be nice to have. Just not sure if /when I'll have time to get to work through all of these. There are more failures than I expected :)

@TomAugspurger
Copy link
Contributor Author

I'm not going to get to this any time soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants