kill11 from ubuntu_ltp_syscalls failed

Bug #1865965 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Confirmed
Undecided
Unassigned
linux (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

 startup='Tue Mar 3 15:46:25 2020'
 tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s
 kill11.c:97: PASS: signal SIGHUP
 kill11.c:97: PASS: signal SIGINT
 kill11.c:97: PASS: signal SIGQUIT dumped core
 kill11.c:97: PASS: signal SIGILL dumped core
 kill11.c:97: PASS: signal SIGTRAP dumped core
 kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core
 kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core
 kill11.c:97: PASS: signal SIGBUS dumped core
 kill11.c:97: PASS: signal SIGFPE dumped core
 kill11.c:97: PASS: signal SIGKILL
 kill11.c:97: PASS: signal SIGUSR1
 kill11.c:97: PASS: signal SIGSEGV dumped core
 kill11.c:97: PASS: signal SIGUSR2
 kill11.c:97: PASS: signal SIGPIPE
 kill11.c:97: PASS: signal SIGALRM
 kill11.c:97: PASS: signal SIGTERM
 kill11.c:97: PASS: signal SIGSTKFLT
 kill11.c:97: PASS: signal SIGXCPU dumped core
 Test timeouted, sending SIGKILL!
 tst_test.c:1269: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1
 tst_test.c:1270: BROK: Test killed! (timeout?)

 Summary:
 passed 18
 failed 0
 skipped 0
 warnings 0
 tag=kill11 stime=1583250385 dur=302 exit=exited stat=2 core=no cu=0 cs=0

Need to see if bump the timeout threshold can help.

Po-Hsu Lin (cypressyew)
tags: added: 4.15 gcp ubuntu-ltp-syscalls xenial
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

With timeout bumped to 15min, this is still failing after:
   kill11.c:97: PASS: signal SIGXCPU dumped core

Need to check if we have this issue with generic kernel.
Or run this manually on GCP nodes to see how long will it take.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This is failing on 4.15 generic kernel as well.

summary: - kill11 from ubuntu_ltp_syscalls failed on X-GCP-4.15
+ kill11 from ubuntu_ltp_syscalls failed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1865965

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Sean Feole (sfeole)
tags: added: kqa-blocker
Sean Feole (sfeole)
tags: added: sru-20200217
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This test would pass if you run it directly:
ubuntu@moe:/opt/ltp/testcases/bin$ sudo ./kill11
tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s
kill11.c:117: INFO: Adjusting RLIMIT_CORE to 524288
kill11.c:97: PASS: signal SIGHUP
kill11.c:97: PASS: signal SIGINT
kill11.c:97: PASS: signal SIGQUIT dumped core
kill11.c:97: PASS: signal SIGILL dumped core
kill11.c:97: PASS: signal SIGTRAP dumped core
kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core
kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core
kill11.c:97: PASS: signal SIGBUS dumped core
kill11.c:97: PASS: signal SIGFPE dumped core
kill11.c:97: PASS: signal SIGKILL
kill11.c:97: PASS: signal SIGUSR1
kill11.c:97: PASS: signal SIGSEGV dumped core
kill11.c:97: PASS: signal SIGUSR2
kill11.c:97: PASS: signal SIGPIPE
kill11.c:97: PASS: signal SIGALRM
kill11.c:97: PASS: signal SIGTERM
kill11.c:97: PASS: signal SIGSTKFLT
kill11.c:97: PASS: signal SIGXCPU dumped core
kill11.c:97: PASS: signal SIGXFSZ dumped core
kill11.c:97: PASS: signal SIGVTALRM
kill11.c:97: PASS: signal SIGPROF
kill11.c:97: PASS: signal SIGIO/SIGPOLL
kill11.c:97: PASS: signal SIGPWR
kill11.c:97: PASS: signal SIGSYS/SIGUNUSED dumped core

Summary:
passed 24
failed 0
skipped 0
warnings 0

Need to check if this is a composite issue with other cases.

tags: added: sru-20200316
Revision history for this message
Sean Feole (sfeole) wrote :

9366. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGHUP
9367. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGINT
9368. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGQUIT dumped core
9369. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGILL dumped core
9370. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGTRAP dumped core
9371. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGIOT/SIGABRT dumped core
9372. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGIOT/SIGABRT dumped core
9373. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGBUS dumped core
9374. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGFPE dumped core
9375. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGKILL
9376. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGUSR1
9377. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGSEGV dumped core
9378. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGUSR2
9379. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGPIPE
9380. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGALRM
9381. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGTERM
9382. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGSTKFLT
9383. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGXCPU dumped core
9384. 07/13 20:30:37 DEBUG| utils:0153| [stdout] Test timeouted, sending SIGKILL!
9385. 07/13 20:30:37 DEBUG| utils:0153| [stdout] tst_test.c:1286: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1
9386. 07/13 20:30:37 DEBUG| utils:0153| [stdout] tst_test.c:1288: BROK: Test killed! (timeout?)

tags: added: bionic sru-20200629
Revision history for this message
Sean Feole (sfeole) wrote :

Also passes when run directly as outlined in comment #4

Sean Feole (sfeole)
Changed in ubuntu-kernel-tests:
status: New → Confirmed
tags: added: hwe
Po-Hsu Lin (cypressyew)
tags: added: 4.4 sru-20200831
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

I tried to run the test staggeringly, all the tests before kill11 followed by kill11 test, to check if it's any test that's causing this issue:
while read line;
do
   echo $line > tmp
   echo "kill11 kill11" >> tmp
   sudo /opt/ltp/runltp -f /home/ubuntu/tmp/tmp
   if [ $? -ne 0 ]; then
       break
   fi
done < ~/syscalls

The ~/syscalls file here is a copy of /opt/ltp/runtests/syscalls, with content after kill11 deleted.

However, I can't reproduce this failure.

I also tried to run those failed test cases on Xenial, fallocate06 fanotify06 fanotify10 kill11, but the kill11 still passed in this case.

I can only reproduce this on Xenial by running the whole syscalls suite.

tags: added: sru-20200921
tags: added: 5.4 aws focal
Revision history for this message
Kelsey Steele (kelsey-steele) wrote :

Spotted on Focal/azure : 5.4.0-1029.29 : amd64

tags: added: azure
Revision history for this message
Kelsey Steele (kelsey-steele) wrote :

Failed on Bionic/oracle : 5.4.0-1026.26~18.04.1 : amd64

tags: added: oracle
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.