Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:6 as permitted sender) client-ip=2620:137:e000::3:6;
Date:   Sat, 9 Dec 2023 09:27:33 +0100
From:   Thomas =?utf-8?Q?Wei=C3=9Fschuh?= <linux@weissschuh.net>
To:     "Paul E. McKenney" <paulmck@kernel.org>
Cc:     linux-kernel@vger.kernel.org, w@1wt.eu,
        Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: nolibc changes for 6.8
Message-ID: <263f4104-f6e0-4b09-84bd-42412ffeff24@t-8ch.de>
References: <4208adae-d185-44a6-a564-ec9bc4c6eb2a@t-8ch.de>
 <25a20ebe-e5af-4ba7-890a-6a9ab121e184@paulmck-laptop>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <25a20ebe-e5af-4ba7-890a-6a9ab121e184@paulmck-laptop>
Precedence: bulk

On 2023-12-08 16:02:27-0800, Paul E. McKenney wrote:
> On Fri, Dec 08, 2023 at 06:09:59PM +0100, Thomas Weißschuh wrote:
> > Hi Paul,
> > 
> > The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:
> > 
> >   Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)
> > 
> > are available in the Git repository at:
> > 
> >   https://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git/ next
> > 
> > for you to fetch changes up to b99c3b15310e7c7cd5f2d843289fe115ab3f8043:
> > 
> >   selftests/nolibc: disable coredump via setrlimit (2023-11-26 11:39:52 +0100)
> 
> Thank you!
> 
> I pulled this in and got the following:
> 
> make run:
> 162 test(s): 162 passed,   0 skipped,   0 failed => status: success
> 
> make run-user:
> 162 test(s): 160 passed,   2 skipped,   0 failed => status: warning
> 
> This looks like complete success to me, but please let me know if this
> is not expected behavior on an x86-64 laptop.

This looks good.

FYI you could also use the new run-tests.sh script.
Prerequisites:
* qemu-user and qemu-system binaries for all supported architectures
* /usr/share/edk2/loongarch64/OVMF_CODE.fd for the loongarch system
  tests
* Pass "-p" the first time to download the toolchains.

$ ./run-tests.sh -m system
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
mips32le:      162 test(s): 161 passed,   1 skipped,   0 failed => status: warning
mips32be:      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

$ ./run-tests.sh -m user
i386:          162 test(s): 160 passed,   2 skipped,   0 failed => status: warning
x86_64:        162 test(s): 160 passed,   2 skipped,   0 failed => status: warning
arm64:         162 test(s): 160 passed,   2 skipped,   0 failed => status: warning
arm:           162 test(s): 160 passed,   2 skipped,   0 failed => status: warning
mips32le:      162 test(s): 159 passed,   3 skipped,   0 failed => status: warning
mips32be:      162 test(s): 159 passed,   3 skipped,   0 failed => status: warning
ppc:           162 test(s): 160 passed,   2 skipped,   0 failed => status: warning
ppc64:         162 test(s): 160 passed,   2 skipped,   0 failed => status: warning
ppc64le:       162 test(s): 160 passed,   2 skipped,   0 failed => status: warning
riscv:         162 test(s): 160 passed,   2 skipped,   0 failed => status: warning
s390:          162 test(s): 159 passed,   3 skipped,   0 failed => status: warning
loongarch:     162 test(s): 158 passed,   3 skipped,   1 failed => status: failure

[ Note: loongarch user is currently broken due to a QEMU bug ]

Thomas