All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhangjin Wu <falcon@tinylab.org>
To: w@1wt.eu
Cc: falcon@tinylab.org, arnd@arndb.de, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-riscv@lists.infradead.org,
	thomas@t-8ch.de
Subject: [PATCH 0/4] selftests/nolibc: fix up and improve test report
Date: Mon,  5 Jun 2023 11:47:41 +0800	[thread overview]
Message-ID: <cover.1685936428.git.falcon@tinylab.org> (raw)

Hi, Willy

Thanks very much for your merge of the v3 generic part1 of rv32, just
tested your latest 20230604-nolibc-rv32+stkp6 branch, everything work
well except a trivial test report regression on the 'run' target.

Besides the fixup, a standalone test-report target added to share them
among run, run-user and re-run and allow independent test report check
via direct 'make test-report'.

Best regards,
Zhangjin
---

Zhangjin Wu (4):
  selftests/nolibc: add a test-report target
  selftests/nolibc: allow run test-report directly
  selftests/nolibc: always print the log file
  selftests/nolibc: fix up test-report for run target

 tools/testing/selftests/nolibc/Makefile | 30 ++++++++++++-------------
 1 file changed, 15 insertions(+), 15 deletions(-)

-- 
2.25.1


WARNING: multiple messages have this Message-ID (diff)
From: Zhangjin Wu <falcon@tinylab.org>
To: w@1wt.eu
Cc: falcon@tinylab.org, arnd@arndb.de, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-riscv@lists.infradead.org,
	thomas@t-8ch.de
Subject: [PATCH 0/4] selftests/nolibc: fix up and improve test report
Date: Mon,  5 Jun 2023 11:47:41 +0800	[thread overview]
Message-ID: <cover.1685936428.git.falcon@tinylab.org> (raw)

Hi, Willy

Thanks very much for your merge of the v3 generic part1 of rv32, just
tested your latest 20230604-nolibc-rv32+stkp6 branch, everything work
well except a trivial test report regression on the 'run' target.

Besides the fixup, a standalone test-report target added to share them
among run, run-user and re-run and allow independent test report check
via direct 'make test-report'.

Best regards,
Zhangjin
---

Zhangjin Wu (4):
  selftests/nolibc: add a test-report target
  selftests/nolibc: allow run test-report directly
  selftests/nolibc: always print the log file
  selftests/nolibc: fix up test-report for run target

 tools/testing/selftests/nolibc/Makefile | 30 ++++++++++++-------------
 1 file changed, 15 insertions(+), 15 deletions(-)

-- 
2.25.1


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2023-06-05  3:48 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05  3:47 Zhangjin Wu [this message]
2023-06-05  3:47 ` [PATCH 0/4] selftests/nolibc: fix up and improve test report Zhangjin Wu
2023-06-05  3:48 ` [PATCH 1/4] selftests/nolibc: add a test-report target Zhangjin Wu
2023-06-05  3:48   ` Zhangjin Wu
2023-06-05  4:18   ` Willy Tarreau
2023-06-05  4:18     ` Willy Tarreau
2023-06-05  6:54     ` Zhangjin Wu
2023-06-05  6:54       ` Zhangjin Wu
2023-06-07  5:52       ` Zhangjin Wu
2023-06-07  5:52         ` Zhangjin Wu
2023-06-07 12:45         ` Willy Tarreau
2023-06-07 12:45           ` Willy Tarreau
2023-06-07 14:15           ` Zhangjin Wu
2023-06-07 14:15             ` Zhangjin Wu
2023-06-05  3:50 ` [PATCH 2/4] selftests/nolibc: allow run test-report directly Zhangjin Wu
2023-06-05  3:50   ` Zhangjin Wu
2023-06-05  3:57 ` [PATCH 3/4] selftests/nolibc: always print the log file Zhangjin Wu
2023-06-05  3:57   ` Zhangjin Wu
2023-06-05  4:20   ` Willy Tarreau
2023-06-05  4:20     ` Willy Tarreau
2023-06-05  7:05     ` Zhangjin Wu
2023-06-05  7:05       ` Zhangjin Wu
2023-06-05  3:58 ` [PATCH 4/4] selftests/nolibc: fix up test-report for run target Zhangjin Wu
2023-06-05  3:58   ` Zhangjin Wu
2023-06-05  4:23   ` Willy Tarreau
2023-06-05  4:23     ` Willy Tarreau
2023-06-05  6:32 ` [PATCH 0/4] selftests/nolibc: fix up and improve test report Willy Tarreau
2023-06-05  6:32   ` Willy Tarreau
2023-06-05 10:53   ` Zhangjin Wu
2023-06-05 10:53     ` Zhangjin Wu
2023-06-06  4:50     ` Willy Tarreau
2023-06-06  4:50       ` Willy Tarreau

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.1685936428.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=linux-riscv@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.