-
Notifications
You must be signed in to change notification settings - Fork 697
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
testing/py-execnet: new aport #6060
Conversation
Tests are outdated (tox), so they cannot complete on current version of pytest/tox combo. Currently I left them in code, but option="!check". If its preferable to completely remove them (without hoping they ever get to be fixed?), it can be done and I'm okay with that. |
dfdecf6
to
ea60392
Compare
ea60392
to
8f1a5ec
Compare
Let's add |
Tests got fixed in official repo, but sadly not yet part of any existing release. Once release happens, we can enable them right after. |
If tests are fixed then we can add patch from commits |
I guess we need https://github.com/pytest-dev/execnet/pull/90.patch |
Might be risks with that as master branch might have changed definition of functions since last release (this pytest is not the only commit that was done since release). Unless we apply all the tree patches since last release... Also another fix is also required to be as patch probably. |
Depends on #6059