From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Shuah Khan <shuah@kernel.org>, Zhangjin Wu <falcon@tinylab.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] selftests/nolibc: various build improvements
Date: Thu, 2 Nov 2023 09:50:38 +0100 [thread overview]
Message-ID: <ZUNi3vsOSIxi49Ph@1wt.eu> (raw)
In-Reply-To: <20231031-nolibc-out-of-tree-v1-0-47c92f73590a@weissschuh.net>
On Tue, Oct 31, 2023 at 09:36:57PM +0100, Thomas Weißschuh wrote:
> With the out-of-tree builds it's possible do incremental tests fairly fast:
>
> time ./run-tests.sh
> i386: 162 test(s): 162 passed, 0 skipped, 0 failed => status: success
> x86_64: 162 test(s): 162 passed, 0 skipped, 0 failed => status: success
> arm64: 162 test(s): 162 passed, 0 skipped, 0 failed => status: success
> arm: 162 test(s): 162 passed, 0 skipped, 0 failed => status: success
> mips: 162 test(s): 161 passed, 1 skipped, 0 failed => status: warning
> ppc: 162 test(s): 162 passed, 0 skipped, 0 failed => status: success
> ppc64: 162 test(s): 162 passed, 0 skipped, 0 failed => status: success
> ppc64le: 162 test(s): 162 passed, 0 skipped, 0 failed => status: success
> riscv: 162 test(s): 162 passed, 0 skipped, 0 failed => status: success
> s390: 162 test(s): 161 passed, 1 skipped, 0 failed => status: warning
> loongarch: 162 test(s): 161 passed, 1 skipped, 0 failed => status: warning
>
> real 1m56.226s
> user 2m42.457s
> sys 0m57.979s
>
> This is with an incremental kernel rebuild and testrun inside qemu.
>
> ---
> Changes in v2:
> - Drop already applied qemu-system-ppc64le patch
> - Drop config generation patch
> - Add Co-developed-by for out-of-tree patch
> - Link to v1: https://lore.kernel.org/lkml/20231010-nolibc-out-of-tree-v1-0-b6a263859596@weissschuh.net/
Thanks Thomas for these, feel free to merge them!
Willy
next prev parent reply other threads:[~2023-11-02 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 20:36 [PATCH 0/3] selftests/nolibc: various build improvements Thomas Weißschuh
2023-10-31 20:36 ` [PATCH 1/3] selftests/nolibc: use EFI -bios for LoongArch qemu Thomas Weißschuh
2023-11-02 8:49 ` Willy Tarreau
2023-10-31 20:36 ` [PATCH 2/3] selftests/nolibc: anchor paths in $(srcdir) if possible Thomas Weißschuh
2023-10-31 20:37 ` [PATCH 3/3] selftests/nolibc: support out-of-tree builds Thomas Weißschuh
2023-11-02 8:50 ` Willy Tarreau [this message]
2023-11-02 19:45 ` [PATCH 0/3] selftests/nolibc: various build improvements Thomas Weißschuh
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=ZUNi3vsOSIxi49Ph@1wt.eu \
--to=w@1wt.eu \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=shuah@kernel.org \
/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