clock_settime01 from ubuntu_ltp_syscalls failed on D-KVM

[Po-Hsu Lin]

Issue found on D-kvm (5.0.0-1021.22-kvm) and 5.0 GCP (5.0.0-1024.24~18.04.1-gcp)

 tag=clock_settime01 stime=1571837742 dur=0 exit=exited stat=1 core=no cu=0 cs=0 startup='Wed Oct 23 13:35:42 2019'
 tst_buffers.c:55: INFO: Test is using guarded buffers
 tst_test.c:1137: INFO: Timeout per run is 0h 05m 00s
 clock_settime01.c:48: FAIL: clock_settime(2): could not advance time
 clock_settime01.c:66: FAIL: clock_settime(2): could not recede time

 Summary:
 passed 0
 failed 2
 skipped 0
 warnings 0

[Po-Hsu Lin (cypressyew)]

This issue could be found on B-GKE-5.0 (5.0.0-1026.27~18.04.2) with instance f1.micro

 startup='Sat Nov 30 00:18:01 2019'
 tst_buffers.c:55: INFO: Test is using guarded buffers
 tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
 clock_settime01.c:48: FAIL: clock_settime(2): could not advance time
 clock_settime01.c:66: FAIL: clock_settime(2): could not recede time

 Summary:
 passed 0
 failed 2
 skipped 0
 warnings 0

[Thadeu Lima de Souza Cascardo (cascardo)]

Maybe this is the same issue as we have fixed for other set time tests. LP: #1845620 inspired yet another fix that included clock_settime, so maybe this will be fixed on the next run.

Cascardo.

[Po-Hsu Lin (cypressyew)]

Hi Thadeu,
I can see this issue on GKE 5.3 (5.3.0-1011.12~18.04.1)

I think it might be the test case name issue:
        return testname[0] in ['leapsec01','stime01','settimeofday01','clock_settime'] and self.series != 'trusty'

clock_settime should be clock_settime01 here, I will change this and give it a try.

[Po-Hsu Lin (cypressyew)]

https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=9e5f818bb0a8bce431c4dfb4269a366c6c14724a