-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Pytest Failing with new Release (4.1.0) #4606
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
Comments
Ah yes, I'll make a quick release today or tomorrow. |
Cool, thanks for the quick response! |
Closing in favor of pytest-dev/pytest-cov#252. |
Thank you very much guys, especially for the quick response. |
kaiwalyajoshi
added a commit
to d2iq-archive/dcos-commons
that referenced
this issue
Jan 16, 2019
…d upstream as mentioned here: pytest-dev/pytest#4606 (comment) Quoted here incase that link breaks in the future: "We have removed item.get_marker, users should use item.get_closest_marker now (it's a long history, this was not an arbitrary change). Indeed I suspect pytest-cov might need to be updated." item.get_marker was removed in this PR pytest-dev/pytest#4564
kaiwalyajoshi
added a commit
to d2iq-archive/dcos-commons
that referenced
this issue
Feb 21, 2019
…d upstream as mentioned here: pytest-dev/pytest#4606 (comment) Quoted here incase that link breaks in the future: "We have removed item.get_marker, users should use item.get_closest_marker now (it's a long history, this was not an arbitrary change). Indeed I suspect pytest-cov might need to be updated." item.get_marker was removed in this PR pytest-dev/pytest#4564
kaiwalyajoshi
added a commit
to d2iq-archive/dcos-commons
that referenced
this issue
Feb 22, 2019
* Replace item.get_marker with item.get_closest_marker as it was removed upstream as mentioned here: pytest-dev/pytest#4606 (comment) Quoted here incase that link breaks in the future: "We have removed item.get_marker, users should use item.get_closest_marker now (it's a long history, this was not an arbitrary change). Indeed I suspect pytest-cov might need to be updated." item.get_marker was removed in this PR pytest-dev/pytest#4564 * Determine security mode of the cluster by querying the cluster instead of a local environment-variable. * Remove underscores from services names, this breaks for scenarios such as 'nonessential_tasks' where underscores are not allowed in task names. * Update frameworks/helloworld/tests/scale/test_scale.py Co-Authored-By: kaiwalyajoshi <[email protected]> * Address comments from code-review * Add support for soack configuration and custom service names, this can be used to differentiate the various hello-worlds. ie --service-name='orchestration/hello-world'
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello everybody,
I encounter that my Travis CI Build fails with the latest (2 hours old) Release of pytest 4.1.0.
The Error i get, for each Test, looks like this :
My conftest.py consists only of these 4 fixtures:
Finally we run the following command in Travis
pipenv run pytest --cov=./
I do not believe that the Tests i run with those fixtures are explicitly relevant for this Error so i only describe what i do with them: I basically call
hasattr()
,isinstance()
orissubclass()
and a few basicassert A == B
calls.I allready looked into the Changelog and the docs if something corresponding to this error has changed but couldn't find anything. From this point i could only speculate that the new Release breakes something with the pytest_cov Plugin (or visversa).
Any help on how to get this working is appreciated.
Thanks in advance.
The text was updated successfully, but these errors were encountered: