All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
	linuxppc-dev@lists.ozlabs.org,
	LKML <linux-kernel@vger.kernel.org>,
	Madhavan Srinivasan <maddy@linux.ibm.com>
Subject: Re: [main-line][PowerPC]selftests/powerpc/signal: sigfuz fails
Date: Mon, 17 Mar 2025 22:13:41 +1100	[thread overview]
Message-ID: <87v7s7di56.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <5f88a95b-1c8d-4a74-9753-9cdb2e64daf4@linux.ibm.com>

Venkat Rao Bagalkote <venkat88@linux.ibm.com> writes:
> Greetings!!
>
> I am observing selftests/powerpc/signal:sigfuz test fails on linux 
> mainline repo on IBM Power10 systems.
>
> The test passes on the kernel with commit head: 
> 619f0b6fad524f08d493a98d55bac9ab8895e3a6 and fails on the kernel with 
> commit head: ce69b4019001407f9cd738dd2ba217b3a8ab831b on the main line.
>
>
> Repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>
> I tried to do git bisect and the bisect tool pointed first bad commit 
> to: 16ebb6f5b6295c9688749862a39a4889c56227f8.
>
> But upon reverting the first bad commit issue is still seen. So please 
> ignore, if the bisection dosent help.
>
>
> Error:
>
> # selftests: powerpc/signal: sigfuz
> # test: signal_fuzzer
> # tags: git_version:v6.14-rc7-1-g49c747976afa
> # !! killing signal_fuzzer
> # !! child died by signal 15
> # failure: signal_fuzzer
> not ok 3 selftests: powerpc/signal: sigfuz # exit=1

That error means the test is timing out and being killed by the test
harness.

That could be due to a bug, but it could just be that your system is
overloaded or something. You can increase the timeout in the code by
adding a call to test_harness_timeout().

The test also includes lots of randomisation, so if you actually need to
bisect it you'd want to change the code to use a consistent random seed
in the calls to srand().

cheers


  reply	other threads:[~2025-03-17 11:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17  9:46 [main-line][PowerPC]selftests/powerpc/signal: sigfuz fails Venkat Rao Bagalkote
2025-03-17 11:13 ` Michael Ellerman [this message]
2025-03-18 10:50   ` Madhavan Srinivasan
2025-03-19 11:44     ` Venkat Rao Bagalkote
2025-03-19 11:57     ` Venkat Rao Bagalkote

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=87v7s7di56.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=venkat88@linux.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.