stime01 from ubuntu_ltp_syscalls failed on D Power9

Bug #1845620 reported by Po-Hsu Lin on 2019-09-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Undecided
Unassigned
linux (Ubuntu)
Undecided
Unassigned
Disco
Undecided
Unassigned

Bug Description

This failure can only be found on Disco Power9, passed on other arches.
Probably a glitch that similar to the hwclock test failure (bug 1802233)

 tag=stime01 stime=1568943645 dur=-22 exit=exited stat=1 core=no cu=0 cs=0
 startup='Fri Sep 20 01:40:45 2019'
 tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s
 stime_var.h:45: INFO: Testing libc stime()
 stime01.c:46: INFO: pt.tv_sec: 1568943675
 stime01.c:47: PASS: system time was set to 1568943675
 tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s
 stime_var.h:48: INFO: Testing SYS_stime syscall
 stime01.c:51: FAIL: system time not set to 1568943705 (got: 1568943660)
 tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s
 stime_var.h:51: INFO: Testing SYS_settimeofday syscall
 stime01.c:46: INFO: pt.tv_sec: 1568943690
 stime01.c:47: PASS: system time was set to 1568943690

 Summary:
 passed 2
 failed 1
 skipped 0
 warnings 0

Po-Hsu Lin (cypressyew) on 2019-09-27
tags: added: disco ppc64el sru-20190902
tags: added: ubuntu-ltp-syscalls

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 1845620

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
Changed in linux (Ubuntu Disco):
status: New → Incomplete
Po-Hsu Lin (cypressyew) wrote :

Issue found on D-KVM (5.0.0-1021.22-kvm)

 startup='Wed Oct 23 14:17:20 2019'
 tst_test.c:1137: INFO: Timeout per run is 0h 05m 00s
 stime_var.h:45: INFO: Testing libc stime()
 stime01.c:51: FAIL: system time not set to 1571840270 (got: 1571840240)
 tst_test.c:1137: INFO: Timeout per run is 0h 05m 00s
 stime_var.h:48: INFO: Testing SYS_stime syscall
 stime_var.h:27: CONF: syscall(-1) __NR_stime not supported
 tst_test.c:1137: INFO: Timeout per run is 0h 05m 00s
 stime_var.h:51: INFO: Testing SYS_settimeofday syscall
 stime01.c:46: INFO: pt.tv_sec: 1571840270
 stime01.c:47: PASS: system time was set to 1571840270

 Summary:
 passed 1
 failed 1
 skipped 0
 warnings 0

tags: added: sru-20191021
tags: added: amd64 linux-kvm
Po-Hsu Lin (cypressyew) wrote :

This issue can be found on B-GKE-5.0

but all 2 tests were failed:
 startup='Sat Nov 30 01:03:14 2019'
 tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
 stime_var.h:45: INFO: Testing libc stime()
 stime01.c:51: FAIL: system time not set to 1575075824 (got: 1575075794)
 tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
 stime_var.h:48: INFO: Testing SYS_stime syscall
 stime_var.h:27: CONF: syscall(-1) __NR_stime not supported
 tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
 stime_var.h:51: INFO: Testing SYS_settimeofday syscall
 stime01.c:51: FAIL: system time not set to 1575075824 (got: 1575075794)

 Summary:
 passed 0
 failed 2
 skipped 0
 warnings 0

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers