Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Zhangjin Wu <falcon@tinylab.org>
To: w@1wt.eu
Cc: arnd@arndb.de, falcon@tinylab.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, thomas@t-8ch.de
Subject: [PATCH v2 0/3] selftests/nolibc: improve test report support
Date: Mon, 19 Jun 2023 14:52:31 +0800	[thread overview]
Message-ID: <cover.1687156559.git.falcon@tinylab.org> (raw)

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

Also did 'run-user' for x86, mips and arm64.

Changes from v1 -> v2:

1. selftests/nolibc: add a standalone test report macro

  As Willy pointed out, the old method with additional test-report
  target not work in 'make -j'.

  A new macro is added to share the same report logic among the
  run-user, run and rerun targets, the path to test log file is 

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.

3. selftests/nolibc: restore the failed tests print

  Restore printing of the failed tests to avoid manually opening
  the test log file when there are really failues.

Best regards,
Zhangjin
---
[1]: https://lore.kernel.org/lkml/cover.1685936428.git.falcon@tinylab.org/
[2]: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git/

Zhangjin Wu (3):
  selftests/nolibc: add a standalone test report macro
  selftests/nolibc: always print the path to test log file
  selftests/nolibc: restore the failed tests print

 tools/testing/selftests/nolibc/Makefile | 19 +++++++------------
 1 file changed, 7 insertions(+), 12 deletions(-)

-- 
2.25.1


             reply	other threads:[~2023-06-19  6:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19  6:52 Zhangjin Wu [this message]
2023-06-19  6:56 ` [PATCH v2 1/3] selftests/nolibc: add a standalone test report macro Zhangjin Wu
2023-06-19  6:57 ` [PATCH v2 2/3] selftests/nolibc: always print the path to test log file Zhangjin Wu
2023-06-19  7:01 ` [PATCH v2 3/3] selftests/nolibc: restore the failed tests print Zhangjin Wu
2023-07-02 16:43 ` [PATCH v2 0/3] selftests/nolibc: improve test report support Willy Tarreau
2023-07-03 16:24   ` Zhangjin Wu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1687156559.git.falcon@tinylab.org \
    --to=falcon@tinylab.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=thomas@t-8ch.de \
    --cc=w@1wt.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox