-
Notifications
You must be signed in to change notification settings - Fork 487
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
[1.11][BACKPORT] 7491 from master: Fix tox failure by pinning pytest dependency. #7496
Conversation
@mesosphere-mergebot test all |
Successfully triggered checks:teamcity/dcos/build/tox |
@mesosphere-mergebot test all |
This repo has @mesosphere-mergebot integration. You can perform the following commands by submitting a comment. Submit a comment with content "@mesosphere-mergebot help" to view more detailed help text and examples. Be sure the have a look at the mergebot documentation, too.
|
Successfully triggered checks:teamcity/dcos/build/tox |
Enterprise Bump PR: mesosphere/dcos-enterprise/pull/8074 |
@mesosphere-mergebot bump-ee |
Enterprise Bump mesosphere/dcos-enterprise/pull/8074 updated. |
👋 This PR has been inactive for 7 days. Please review the status checks to see what needs to be done to move it forward or change the label to Work in Progress. Thank you! |
13 similar comments
👋 This PR has been inactive for 7 days. Please review the status checks to see what needs to be done to move it forward or change the label to Work in Progress. Thank you! |
👋 This PR has been inactive for 7 days. Please review the status checks to see what needs to be done to move it forward or change the label to Work in Progress. Thank you! |
👋 This PR has been inactive for 7 days. Please review the status checks to see what needs to be done to move it forward or change the label to Work in Progress. Thank you! |
👋 This PR has been inactive for 7 days. Please review the status checks to see what needs to be done to move it forward or change the label to Work in Progress. Thank you! |
👋 This PR has been inactive for 7 days. Please review the status checks to see what needs to be done to move it forward or change the label to Work in Progress. Thank you! |
👋 This PR has been inactive for 7 days. Please review the status checks to see what needs to be done to move it forward or change the label to Work in Progress. Thank you! |
👋 This PR has been inactive for 7 days. Please review the status checks to see what needs to be done to move it forward or change the label to Work in Progress. Thank you! |
👋 This PR has been inactive for 7 days. Please review the status checks to see what needs to be done to move it forward or change the label to Work in Progress. Thank you! |
👋 This PR has been inactive for 7 days. Please review the status checks to see what needs to be done to move it forward or change the label to Work in Progress. Thank you! |
👋 This PR has been inactive for 7 days. Please review the status checks to see what needs to be done to move it forward or change the label to Work in Progress. Thank you! |
👋 This PR has been inactive for 7 days. Please review the status checks to see what needs to be done to move it forward or change the label to Work in Progress. Thank you! |
👋 This PR has been inactive for 7 days. Please review the status checks to see what needs to be done to move it forward or change the label to Work in Progress. Thank you! |
👋 This PR has been inactive for 7 days. Please review the status checks to see what needs to be done to move it forward or change the label to Work in Progress. Thank you! |
This is a backport of the following PR:
#7491
High-level description
Just released version of pytest 6.0.0 causes tox to failure.
This has been resolved by pytest pytest-dev/pytest#7565, however, as we wait for update, we could approach the problem at our end by pinning pytest to previous stable version.
Corresponding DC/OS tickets (required)