Skip to content

CI: --strict option in pytest failing builds #38483

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
jreback opened this issue Dec 15, 2020 · 3 comments · Fixed by #38478
Closed

CI: --strict option in pytest failing builds #38483

jreback opened this issue Dec 15, 2020 · 3 comments · Fixed by #38478
Labels
CI Continuous Integration
Milestone

Comments

@jreback
Copy link
Contributor

jreback commented Dec 15, 2020

seems we are passing --strict to pytest, we must have picked up an updated version and this is now raising: https://dev.azure.com/pandas-dev/pandas/_build/results?buildId=50126&view=logs&j=eab14f69-13b6-5db7-daeb-7b778629410b&t=ce687173-08c6-5301-838d-71b2dda24510

temporarily can just fix the pytest version or just remove this

cc @pandas-dev/pandas-core

@jreback jreback added the CI Continuous Integration label Dec 15, 2020
@jreback jreback added this to the 1.2 milestone Dec 15, 2020
@jreback jreback changed the title CI: --strict option on updates pytest failing builds CI: --strict option in pytest failing builds Dec 15, 2020
@jreback
Copy link
Contributor Author

jreback commented Dec 15, 2020

and @mroeschke alredy has a PR: #38478

@WillAyd
Copy link
Member

WillAyd commented Dec 15, 2020

Is this different from #38478 ?

@jreback
Copy link
Contributor Author

jreback commented Dec 15, 2020

nope i opened the issue then saw the PR (already merged it as well)

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 a pull request may close this issue.

2 participants