Comment 12 for bug 1899416

rtc01 fails on missed alarm on multiple different Azure instances if the
alarm is set for the next minute.

If alarm is set for now+60 seconds, it works fine. Clearly Microsoft
Hyper-V cloud instances have a broken CMOS RTC which unfortunately
cannot be easily fixed. Adding simple workaround to extend the time to
60 seconds allows to avoid false positives in expense of longer testing
time.

Not a Linux kernel issue. Not a LTP issue, although a workaround is proposed.

Patch sent upstream:
https://lists.linux.it/pipermail/ltp/2021-September/024989.html