-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
5.3.4 causing internal errors, as well #6596
Comments
@oseiberts11 |
@oseiberts11 Keep in mind though that the issue with #6517 is known, and might e.g. get triggered when paths/nodeids are rewritten (which might happen especially with Docker, but would require |
The output is short enough that I can paste all of it. I forced the pytest-5.3.4 version here. I experimented a bit with
|
This is fixed in version 5.3.5. Should have been closed by merge of #6614, not sure why it didn't. |
#6517 is closed already, but I want to add some information. There is some finger-pointing to something called "nose", but I see the same problem and I don't use "nose", whatever it is. So a proper fix in the future which only takes "nose" into account may not be perfect.
Fortunately the same workaround (pinning pytest to 5.3.3) works for me.
You can see my test code for instance at syseleven/rebootmgr@cf0ec0b in branch https://github.com/syseleven/rebootmgr/commits/oseibert-os-5267-use-enabled-instead-of-disabled . The next commit adds the workaround.
The weird thing is that all tests succeed, except those in the file
tests/test_lock.py
. As soon as the testing gets there, it fails. This is the case if you run the file on its own, or when you just run all tests (and then this file gets run as second file).You can run the tests in their proper environment with the command
docker-compose run --rm integration_tests_py35
(or 36 or 37).The text was updated successfully, but these errors were encountered: