Venkat Rao Bagalkote <venka...@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
