-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Pin pytest<6 #453
Pin pytest<6 #453
Conversation
Do we still support Appveyor? Should I care that Appveyor failed? |
If the appveyor failure is related, then yes it ideally should be fixed. If it's failing with something unrelated maybe the plug can be pulled in the near future (I'm reluctant to do it as quite a lot of projects used to use ci-helpers outside of astropy, so while this is a bit of a blast from the past at this point, as we see close to home, projects' leaderships may care little to nothing about DevOps leaving projects stuck with obsolete solutions). |
Re: Appveyor failures conda doesn't support Python 2.7 and 3.5 anymore, so those can probably be dropped from the matrix. The rest of the jobs are failing because
|
OK, let's see what a rebuild of the last merge says. 20 days days ago it was still all green. If the rerun lights up the same as this PR, I'm pushing the merge button. |
Sounds like a plan. Thanks, @bsipocz ! |
OK, so appveyor is very badly broken already. Something for another day.... |
Thanks for checking and the merge! |
Need to pin
pytest<6
until a newpytest-doctestplus
with fix for scientific-python/pytest-doctestplus#118 is released. The patch is modeled after what @bsipocz did in #445 but in reverse (if that makes sense...).cc @astrofrog