From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Willy Tarreau <w@1wt.eu>, "Paul E. McKenney" <paulmck@kernel.org>,
linux-kernel@vger.kernel.org
Subject: tools/nolibc: 6.14 pull request
Date: Mon, 13 Jan 2025 23:06:31 +0100 [thread overview]
Message-ID: <990d31c7-ba4f-495e-9146-a3ca0200d8ae@t-8ch.de> (raw)
Hi Shuah,
The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:
Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git tags/nolibc-20250113-for-6.14-1
for you to fetch changes up to 60fe18237f72e3a186127658452dbb0992113cf7:
selftests/nolibc: add configurations for riscv32 (2025-01-13 22:21:34 +0100)
----------------------------------------------------------------
nolibc changes for 6.14
Changes
-------
* Test riscv32 support
* Print an error message if toolchain for run-tests.sh is missing
----------------------------------------------------------------
Thomas Weißschuh (6):
tools/nolibc: add support for waitid()
selftests/nolibc: use waitid() over waitpid()
selftests/nolibc: use a pipe to in vfprintf tests
selftests/nolibc: skip tests for unimplemented syscalls
selftests/nolibc: rename riscv to riscv64
selftests/nolibc: add configurations for riscv32
Willy Tarreau (1):
selftests/nolibc: run-tests.sh: detect missing toolchain
tools/include/nolibc/sys.h | 18 ++++++++++++
tools/testing/selftests/nolibc/Makefile | 11 +++++++
tools/testing/selftests/nolibc/nolibc-test.c | 44 ++++++++++++++++------------
tools/testing/selftests/nolibc/run-tests.sh | 9 +++++-
4 files changed, 63 insertions(+), 19 deletions(-)
Test results:
$ ./run-tests.sh -m user
i386: 195 test(s): 193 passed, 2 skipped, 0 failed => status: warning
x86_64: 195 test(s): 193 passed, 2 skipped, 0 failed => status: warning
arm64: 195 test(s): 193 passed, 2 skipped, 0 failed => status: warning
arm: 195 test(s): 193 passed, 2 skipped, 0 failed => status: warning
mips32le: 195 test(s): 192 passed, 3 skipped, 0 failed => status: warning
mips32be: 195 test(s): 192 passed, 3 skipped, 0 failed => status: warning
ppc: 195 test(s): 193 passed, 2 skipped, 0 failed => status: warning
ppc64: 195 test(s): 193 passed, 2 skipped, 0 failed => status: warning
ppc64le: 195 test(s): 193 passed, 2 skipped, 0 failed => status: warning
riscv32: 195 test(s): 176 passed, 19 skipped, 0 failed => status: warning
riscv64: 195 test(s): 193 passed, 2 skipped, 0 failed => status: warning
s390: 195 test(s): 192 passed, 3 skipped, 0 failed => status: warning
loongarch: 195 test(s): 192 passed, 3 skipped, 0 failed => status: warning
$ ./run-tests.sh -m user -l
i386: 195 test(s): 193 passed, 2 skipped, 0 failed => status: warning
x86_64: 195 test(s): 193 passed, 2 skipped, 0 failed => status: warning
arm64: 195 test(s): 193 passed, 2 skipped, 0 failed => status: warning
arm: 195 test(s): 193 passed, 2 skipped, 0 failed => status: warning
mips32le: 195 test(s): 192 passed, 3 skipped, 0 failed => status: warning
mips32be: 195 test(s): 192 passed, 3 skipped, 0 failed => status: warning
ppc: 195 test(s): 192 passed, 3 skipped, 0 failed => status: warning
ppc64: 195 test(s): 192 passed, 3 skipped, 0 failed => status: warning
ppc64le: 195 test(s): 192 passed, 3 skipped, 0 failed => status: warning
riscv32: 195 test(s): 175 passed, 20 skipped, 0 failed => status: warning
riscv64: 195 test(s): 192 passed, 3 skipped, 0 failed => status: warning
s390: 195 test(s): 192 passed, 3 skipped, 0 failed => status: warning
loongarch: 195 test(s): 192 passed, 3 skipped, 0 failed => status: warning
$ ./run-tests.sh -m system
i386: 195 test(s): 195 passed, 0 skipped, 0 failed => status: success
x86_64: 195 test(s): 195 passed, 0 skipped, 0 failed => status: success
arm64: 195 test(s): 195 passed, 0 skipped, 0 failed => status: success
arm: 195 test(s): 195 passed, 0 skipped, 0 failed => status: success
mips32le: 195 test(s): 194 passed, 1 skipped, 0 failed => status: warning
mips32be: 195 test(s): 194 passed, 1 skipped, 0 failed => status: warning
ppc: 195 test(s): 195 passed, 0 skipped, 0 failed => status: success
ppc64: 195 test(s): 195 passed, 0 skipped, 0 failed => status: success
ppc64le: 195 test(s): 195 passed, 0 skipped, 0 failed => status: success
riscv32: 195 test(s): 178 passed, 17 skipped, 0 failed => status: warning
riscv64: 195 test(s): 195 passed, 0 skipped, 0 failed => status: success
s390: 195 test(s): 194 passed, 1 skipped, 0 failed => status: warning
loongarch: 195 test(s): 194 passed, 1 skipped, 0 failed => status: warning
Thanks,
Thomas
next reply other threads:[~2025-01-13 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 22:06 Thomas Weißschuh [this message]
2025-01-13 23:57 ` Shuah Khan
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=990d31c7-ba4f-495e-9146-a3ca0200d8ae@t-8ch.de \
--to=linux@weissschuh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=skhan@linuxfoundation.org \
--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
all inboxes | Powered by JetHome®