ripe-vase-8556105/04/2022, 6:14 PM
run and having some trouble. Is there a convenient way to write the result summary at the end of a test run to a file or envvar, like`RESULTS=$(./pants test ::)` ? I also tried using pytest plugins to generate summary reports (like
) and they weren’t working, possibly because the full results would have to be aggregated from the parallel test runs. I noticed that the summary (i.e. the list of
at the end of the output) goes to stderr so I added a
𐄂 test:test failed in 1.32s.
, but then it captures other errors too. Is there an easy way to just capture the summary?
witty-crayon-2278605/04/2022, 6:28 PM
ripe-vase-8556105/04/2022, 6:32 PM
don’t work as intended when used with pants test make sense? Ideally I would just be able to use that, or another pytest results aggregator plugin.
witty-crayon-2278605/04/2022, 6:33 PM
would support that
ripe-vase-8556105/04/2022, 6:37 PM
) after the run completed. It says in the logs that in generates files like..
but the files aren’t there. Should they be or is it expected for them to get cleaned up?
witty-crayon-2278605/04/2022, 6:38 PM
ripe-vase-8556105/04/2022, 6:39 PM
witty-crayon-2278605/04/2022, 6:40 PM
an option? iirc @bitter-ability-32190 does that, and we should consider whether if that is helpful to a few folks we need to get quieter by default
ripe-vase-8556105/04/2022, 6:42 PM
bitter-ability-3219005/04/2022, 6:44 PM
because some options like no process cleanup and stats log info and I was tired of trying to track them down for the log level by target whitelist.
It's still a goal of mine to make pants less noisy in CI tho
witty-crayon-2278605/04/2022, 6:49 PM