-
Notifications
You must be signed in to change notification settings - Fork 532
CI: Install pytest>=3.4 in Travis #2659
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
Conversation
it looks like they just had a new release. If you have problem, we can temporary change to 1.22.3, it was working |
That might be a better solution. Hopefully it's just a temporary resolution error and we don't actually have any conflicts that prevent us from using |
Codecov Report
@@ Coverage Diff @@
## master #2659 +/- ##
==========================================
- Coverage 67.62% 67.61% -0.01%
==========================================
Files 340 340
Lines 43054 43054
Branches 5329 5329
==========================================
- Hits 29115 29113 -2
- Misses 13237 13240 +3
+ Partials 702 701 -1
Continue to review full report at Codecov.
|
or can we just merge to master? looks like everyone is happy with pytest>3.4 |
Yeah, updating pip wasn't sufficient to get pip to correctly resolve the dependency. The only alternative I see is to add a @satra @oesteban Any thoughts on the best way to proceed? 3.4 is from this year, so this is a fairly strong constraint for people who don't need the latest |
@effigies - not sure why this is a problem. If they already have old |
Sure. But now we're requiring pytest 3.4. In general, it's good to be as flexible as possible to avoid putting users in a place where they have conflicting requirements. For instance, suppose somebody has a package that requires |
This reverts commit 23a8e0e.
@effigies - so one option would be to remove |
Eh. I decided to go the Travis hack route. It really is just a quirk of Travis' default python environment and a pip bug. Keeping a reasonable set of dependencies shouldn't affect typical users. If I'm wrong, and we need to update the dependency in the future, we can. |
@effigies - but the standard pip installation of nipype will not lead to the error for |
The case in which it does is if you have Sure there might be some setups like that, and we can walk people through some solution that fits their needs. Likely |
ok, we can wait and see if anyone complains |
Summary
pytest-xdist 1.22.4 bumped their requirement to pytest
>=3.4
(ours is>=3.0
). It's unclear why this is failing to resolve. Creating this issue to see if there's a conflict.See Travis errors in #2658.
Possibly related: #2649
Acknowledgment