[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87h6z9ka3s.fsf@oldenburg.str.redhat.com>
Date: Tue, 08 Nov 2022 11:35:03 +0100
From: Florian Weimer <fweimer@...hat.com>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: "open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
lkft-triage@...ts.linaro.org, libc-alpha@...rceware.org,
linux-api@...r.kernel.org,
Christian Brauner <christian.brauner@...ntu.com>,
Shuah Khan <shuah@...nel.org>
Subject: Re: selftests: clone3: clone3_clear_sighand failed - Bail out!
Failed to clear signal handler for child process
* Naresh Kamboju:
> selftests: clone3: clone3_clear_sighand failed on arm32 and i386
> but passed on arm64 and x86_64.
>
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
>
> # selftests: clone3: clone3_clear_sighand
> # TAP version 13
> # 1..1
> # # clone3() syscall supported
> # Bail out! Failed to clear signal handler for child process
> # # Planned tests != run tests (1 != 0)
> # # Totals: pass:0 fail:0 xfail:0 xpass:0 skip:0 error:0
> not ok 2 selftests: clone3: clone3_clear_sighand # exit=1
Not sure why you are reporting this to libc-alpha. We'd like to help,
but there doesn't seem to be anything glibc-specific in this report?
Thanks,
Florian
Powered by blists - more mailing lists