Hi Zhangjin,
On Mon, Jun 19, 2023 at 02:52:31PM +0800, Zhangjin Wu wrote:
> Hi, Willy
>
> Here is the v2 of our old patchset about test report [1].
>
> The trailing '\r' fixup has been merged, so, here only resend the left
> parts with an additional patch to restore the failed tests print.
>
> This patchset is rebased on the dev.2023.06.14a branch of linux-rcu [2].
>
> Tests have passed for 'x86 run':
>
> 138 test(s) passed, 0 skipped, 0 failed.
> See all results in /labs/linux-lab/src/linux-stable/tools/testing/selftests/nolibc/run.out
(...)
> 2. selftests/nolibc: always print the path to test log file
>
> Always print the path to test log file, but move it to a new line to
> avoid annoying people when the test pass without any failures.
I'm still really missing the (s+f > 0) test I added which was a time saver
for me, because I could trivially check in the output reports which ones
were totally OK and which ones required attention. Sure I could also start
to grep for "passed," | grep -v " 0 skipped, 0 failed" but that's quite a
pain, really.
I'm going to merge your series anyway otherwise we'll continue to bikeshed
for many weeks and I know how annoying it is to keep unmerged series. But
I would like that we find a solution that satisfies everyone.
Maybe one possibility would be to add a "status" at the end of the line
that emits "success", "warning", "failure" depending on the highest level
reached like this:
138 test(s) passed, 0 skipped, 0 failed => status: success
136 test(s) passed, 2 skipped, 0 failed => status: warning
136 test(s) passed, 1 skipped, 1 failed => status: failure
This way it's easy to grep -v "status: success" or grep "status: failure"
to instantly get the corresponding details and also grep for them from
multiple files.
Thanks!
Willy
