With the new patch landed, a manual test on Power9 shows positive result on
stime01.
I think this can be closed now.
(Please feel free to re-open it if you still seeing this somewhere else)
Thanks!
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
--
You received
Found out that we needed to fix how to verify the lines, so I pushed
such a fix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1845620
Title:
stime01 from ubuntu_ltp_syscalls failed on
Do you have a link to the entire result?
Cascardo.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1845620
Title:
stime01 from ubuntu_ltp_syscalls failed on D Power9
Status in
I have the patch tested on Power9 node "baltar" with Disco kernel (5.0.0-37).
It's still failing with this stime01 test.
startup='Wed Dec 25 10:25:31 2019'
tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
stime_var.h:45: INFO: Testing libc stime()
stime01.c:46: INFO: pt.tv_sec: 1577269561
Well, we were already doing it on autotest-client-tests side, so I sent
a patch that sfeole "acked", but didn't apply. So, I just applied it.
Please, watch if future runs are still broken anyhow.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Sounds like a good plan, please feel free to sent out the patch for ACT
(or even better, to the upstream LTP project!)
Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1845620
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: ubuntu-kernel-tests
Status: New => In Progress
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Thadeu Lima de Souza
Not sure why I couldn't reproduce it on my amd64, but this does not fail
after I stop systemd-timesyncd. Well, you managed to find it on GKE,
which is not ppc64el, so good enough.
stime and settimeofday should not be fiddling with hwclock, only system
time. Maybe we should stop systemd-timesync
Can be found on Eoan generic (5.3.0-25.27) P9 as well. This issue was
not spotted on Eoan P8.
** Tags added: sru-20191202
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1845620
Title:
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:
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
11 matches
Mail list logo
