-
Notifications
You must be signed in to change notification settings - Fork 102
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
use only pytest < 3 #4886
use only pytest < 3 #4886
Conversation
Is pytest causing any other issues? If none, cfbfac9 is probably we should be doing anyway in our tests. i.e. this could be our fault not pytests. |
do you want me to drop pytest cap and cherry-pick |
I also don't understand why merge integration shows:
virtualenv has no pytests installed |
This was the comment on the initial PR |
I don't think pytest-dev/pytest#1908 was enough. It only made it possible to accept |
@joshmoore thanks |
Test failure occurred with pytest-3.0.2 in devspace.
#4853 cherry-picked |
--rebased-to #4894 |
Filed a card to remember to uncap pytest: https://trello.com/c/TcfoKhbw/723-uncap-pytest . Merging. |
What this PR does
try to fix pytest version
Testing this PR
go to:
and check which version is used when tests are run, it is listed in:
Related reading
#4826
LIMITATIONS:
for some reason merge build has pytest-2.8.1 installed, that is not very clear to me where is that exactly. This PR run on merge didn't change anything, see #4886 (comment)