Skip to content

Revert "Pin pytest to <3.8 (for 3.0.x)" #13159

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

Merged
merged 1 commit into from
Jan 12, 2019

Conversation

dstansby
Copy link
Member

Reverts #12878. Should fix CI for 3.0.x

@dstansby
Copy link
Member Author

Well it's slightly less broken now...

@QuLogic
Copy link
Member

QuLogic commented Jan 12, 2019

You would need #12154 I think, but it'd bump minimum pytest.

@timhoffm
Copy link
Member

IMO it‘s not a problem to bump the pytest requirement for 3.0.x

@dstansby
Copy link
Member Author

I'll merge this then since it's step 1 to fixing the tests.

@dstansby dstansby merged commit e43acae into v3.0.x Jan 12, 2019
@dstansby dstansby added this to the v3.0.3 milestone Jan 12, 2019
@dstansby dstansby deleted the revert-12878-fix-pytest-error-in-ci branch January 12, 2019 17:59
@tacaswell
Copy link
Member

@meseeksdev backport to v3.0.x

@dstansby the milestone needs to be set before the PR is merged for the bot to do it automatically.

@tacaswell
Copy link
Member

@meeseeksdev backport to v3.0.x

@lumberbot-app
Copy link

lumberbot-app bot commented Jan 12, 2019

Can't Dooooo.... It seem like this is already backported (commit is empty).I won't do anything. MrMeeseeks out.

@QuLogic
Copy link
Member

QuLogic commented Jan 12, 2019

This is a backport already.

@tacaswell
Copy link
Member

🐑 sorry for reading comprehension failure.

QuLogic added a commit that referenced this pull request Jan 22, 2019
…154-on-v2.2.x

Backport PRs #12154, #12294, #12297, #12316, #13159 & #13205 to fix multiple tests issues
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants