Provide a way to reduce the diagnostic output #256
Comments
|
Original comment by @jayvdb I would also appreciate a quieter tox for linter tasks, as the errors are drowned in noise. ( https://phabricator.wikimedia.org/T117570 ) |
|
Original comment by @AndreLouisCaron I'm willing to give a go at this. Any suggestions for the implementation? |
|
Original comment by @The-Compiler I agree this would be useful - I also run some linters via tox, and the output for those currently looks rather cluttered (33/58 lines by tox): How do you think the UI for this should look? Just a If nobody else steps up, I might have time next week to submit a PR. |
|
I would need to have a This is because I have a use case that runs tox as part of a test. I would need to have no output at all if everything goes well, and full diagnostic output if |
|
Any updates on this? Somehow I find weird the fact that adding |
obestwalter
added
area:reporting
feature:new
|
Hi @ssbarnea a PR implementing this would very likely be merged, but nobody is working on this. |
|
@obestwalter I can understand why this I have few projects that do have like 6-20 tox targets and most of them are re-used in order speedup testing but for each of them I am forced to see the result of pip freeze. I think that 80% of the console output is taken only by the |
|
Good point. This might actually be much easier to fix then ans should be treated differently. Could you open a new issue outlining this? Thanks. |
|
Added as #601 |
|
@gaborbernat I don't think this issue should have been closed. I'm not sure exactly what #601 does, but it doesn't address the original request, which was to have tox be less verbose in general. Unless I'm misunderstanding something... |
Sometimes the output of tox in addition to the output of the command(s) tox is running can be a overwhelming and confusing. Allowing users to silence tox's output is incredibly useful in focusing on the command(s)'s output. Resolves tox-dev#256
* Add a -q (quiet) option to tox Sometimes the output of tox in addition to the output of the command(s) tox is running can be a overwhelming and confusing. Allowing users to silence tox's output is incredibly useful in focusing on the command(s)'s output. Resolves #256 * Add a changelog item and add myself to contributors * Rephrase our changelog item and fixup change Use a class to contain named constants to replace all the magic numbers used in the reporter. Further, rename the parsed values from the command-line.
When I run my tests, tox prints a number of lines of information. This is helpful when things are going wrong, but I don't need to see them on every test run.
Here there are 11 lines of output. Five are from tox, and I would like to suppress them.
The text was updated successfully, but these errors were encountered: