nsleep-lat from timers in ubuntu_kernel_selftests failed on B-aws-5.4 / F-arm64 / F-azure 5.8

Can be found on B-gke-5.3
# selftests: timers: nsleep-lat
# nsleep latency CLOCK_REALTIME [OK]
# nsleep latency CLOCK_MONOTONIC [OK]
# nsleep latency CLOCK_MONOTONIC_RAW [UNSUPPORTED]
# nsleep latency CLOCK_REALTIME_COARSE [UNSUPPORTED]
# nsleep latency CLOCK_MONOTONIC_COARSE [UNSUPPORTED]
# nsleep latency CLOCK_BOOTTIME [OK]
# nsleep latency CLOCK_REALTIME_ALARM [OK]
# nsleep latency CLOCK_BOOTTIME_ALARM [OK]
# nsleep latency CLOCK_TAI Large abs latency: 3604330207 ns :[FAILED]
# Bail out!
# # Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0
not ok 3 selftests: timers: nsleep-lat # exit=1

Note for comment it's n1-highcpu-16 with 5.3.0-1033.35-gke

This can be found on Focal ARM64 as well (passed on other arches).

The node in comment #3 is hotdog-kernel

Seen with linux-aws 4.15.0-1094.101 on t3.medium.

Seen with focal linux 5.4 on blanka during cycle sru-20210510.

Found on focal/azure 5.8.0-1034.36~20.04.1-azure instance Standard_B1ms (passes on others).

Cannot reproduce anymore on 5.8.0-1034.36~20.04.1-azure instance Standard_B1ms, might be some misinterpretation of results.

Happened on node fozzie.i386 with bionic:4.15.0-154.161 (lowlatency) for sru-20210719:

[stdout] nsleep latency CLOCK_TAI Large abs latency: 3652996094 ns :[FAILED]

Found on 2021.09.27/bionic/linux-fips/4.15.0-1071.80 (node lagalla.amd64).

Found on bionic/linux-gcp-fips: 4.15.0-2020.22 - n1-standard-2

Found on bionic/linux-gcp-fips: 4.15.0-2021.23 - g1-small