This passed in other cycles with # Estimating clock drift: 0.0(est) 0.0(act) [OK]
but is now failing because it seems the function clock_gettime* in the test is now actually returning a value when it was not before.
Regardless this seems like a case of vm clock flakiness. Maybe something in glibc changed that caused this to finally return a value for some reason? Havent looked into it too much but doesent seem like a kernel issue.
Found on 2022.01. 31/impish/ kvm/5.13. 0-1013. 14 and 2022.01. 31/bionic/ kvm/4.15. 0-1107. 109 and is failing with
19:54:27 DEBUG| [stdout] # selftests: timers: raw_skew
19:56:27 DEBUG| [stdout] # Estimating clock drift: 43.443(est) 0.0(act) [FAILED]
19:56:27 DEBUG| [stdout] # # Totals: pass:0 fail:0 xfail:0 xpass:0 skip:0 error:0
19:56:27 DEBUG| [stdout] not ok 1 selftests: timers: raw_skew # exit=1
This passed in other cycles with # Estimating clock drift: 0.0(est) 0.0(act) [OK]
but is now failing because it seems the function clock_gettime* in the test is now actually returning a value when it was not before.
Regardless this seems like a case of vm clock flakiness. Maybe something in glibc changed that caused this to finally return a value for some reason? Havent looked into it too much but doesent seem like a kernel issue.