From: Christian Brauner <brauner@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: "open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org, Florian Weimer <fweimer@redhat.com>,
libc-alpha@sourceware.org, linux-api@vger.kernel.org,
Christian Brauner <christian.brauner@ubuntu.com>,
Shuah Khan <shuah@kernel.org>
Subject: Re: selftests: clone3: clone3_clear_sighand failed - Bail out! Failed to clear signal handler for child process
Date: Tue, 8 Nov 2022 11:04:20 +0100 [thread overview]
Message-ID: <20221108100420.6zhmrio226vbii4e@wittgenstein> (raw)
In-Reply-To: <CA+G9fYs+fOTBO=aTfO57xby=QQDaqUt4umwgo6bwLB_iGoSEPw@mail.gmail.com>
On Tue, Nov 08, 2022 at 03:28:55PM +0530, Naresh Kamboju wrote:
> selftests: clone3: clone3_clear_sighand failed on arm32 and i386
> but passed on arm64 and x86_64.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.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
>
> Test details links,
> https://lkft.validation.linaro.org/scheduler/job/5820146#L1795
>
> Test results comparison link,
> https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20221107/testrun/12848543/suite/kselftest-clone3/test/clone3.clone3_clear_sighand/history/
Seems before 27 September 2022 this test wasn't run on 32bit instances
and noone ever noticed?
next prev parent reply other threads:[~2022-11-08 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 9:58 selftests: clone3: clone3_clear_sighand failed - Bail out! Failed to clear signal handler for child process Naresh Kamboju
2022-11-08 10:04 ` Christian Brauner [this message]
2022-11-08 10:21 ` Naresh Kamboju
2022-11-08 11:25 ` Christian Brauner
2022-11-08 10:35 ` Florian Weimer
2022-11-08 10:53 ` Naresh Kamboju
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=20221108100420.6zhmrio226vbii4e@wittgenstein \
--to=brauner@kernel.org \
--cc=christian.brauner@ubuntu.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).