-
Notifications
You must be signed in to change notification settings - Fork 243
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
pytest 3.0.0 captures all or nothing #375
Comments
Hi @fenchu, thank you for opening this issue! I had a question before I dig any deeper though. Is your issue with pytest or pytest-html? Also, could you please paste the output of |
Hi Thanks for looking into this. Would be nice to minimize test output. Or a workaround via conftest.py and fixtures.
pytest seem to be fine, this is what I like to log in the report: (below is ubuntu 16.04LTS container, it is exactly the same output in windows):
If I use pytest-html:
and if I dig into the html file, it logs anything (lynx output of test1.html in container)
|
it is the same with pytest-html3..1.1:
pytest 6.2.1 and pytest-html 2.1.1 works fine, so I'm pretty sure it is in pytest-html |
I forked the v3.1.1 and added a filter so it only captures the stderr or file, also sets screenshots on a new line after log at a fixed size also clicking on screenshots open in new window and some more robust decoding of files
|
Hi , is there anything about this issue ? I want to capture only the log calls, instead its all or nothing indeed. |
my packages are these but got same issue: Package Version
----------------------------- -----------
alabaster 0.7.12
ansi2html 1.7.0
astroid 2.11.6
asttokens 2.0.5
......
pytest 7.1.2
pytest-cov 3.0.0
pytest-forked 1.4.0
pytest-html 3.1.1
pytest-icdiff 0.5
pytest-metadata 2.0.1
pytest-mock 3.7.0
pytest-sugar 0.9.4
pytest-tldr 0.2.4
pytest-xdist 2.5.0
python-dateutil 2.8.2
python-docx 0.8.11
python-gitlab 3.5.0 |
Sorry that you're having issues and that this has lingered for so long. I will make sure to revisit this for v4.x which is going to be in beta in a week or two. Hopefully, with the complete rebuild we're doing for v4, this won't be an issue. |
With pytest 2.1.1 I could finegrain my logs and only capture stdout etc. But when I upgraded to v3.0.0 there was "No log output captured." allover, and I'm only able switch between all or nothing the -s and --capture settings:
How can I finegrain this in the new version, or is the a way I can hack this in a fixture.
The text was updated successfully, but these errors were encountered: