On 09/10/13 21:56, Andrew Gregory wrote:
On 10/09/13 at 02:20pm, Allan McRae wrote:
On 03/10/13 02:04, Jeremy Heiner wrote:
My experience (limited as it is) suggests that the truncation is still helpful de-cluttering when you aren't debugging rules. Running manually let me narrow the selection of tests (e.g. tests/querycheck00[125].py). When I was working on rules then I usually narrowed to the one file I was editing and wanted to see the full rules, so "-v". But at other times I wanted to run tests/query*.py, and then the full rules were somewhat of a distraction from my task.
Can someone provide examples of the two different outputs and clarify to me where ther are (i.e. terminal, file)?
Allan
They're printed by pactest. Since the automake integration, they get redirected to files during `make check`, but still get printed to the terminal when running pactest directly.
diff -r tests/query006.log tests-trunc/query006.log 9,10c9,10 < ok 3 - PACMAN_OUTPUT=^Description.*Overflow size and date values if possible < ok 4 - PACMAN_OUTPUT=^Installed Size.*9765625.00 KiB ---
ok 3 - PACMAN_OUTPUT=^Description.*Overflow ... ok 4 - PACMAN_OUTPUT=^Installed Size.*976562...
I agree with getting rid of the truncation altogether. Not many lines will go over the standard terminal width anyway. A