From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2] rtc01: add workaround for broken CMOS RTC on Microsoft Hyper-V cloud
Date: Fri, 10 Sep 2021 10:34:48 +0200 [thread overview]
Message-ID: <YTsYqBJP8oWiuEGQ@yuki> (raw)
In-Reply-To: <20210909163326.42598-2-krzysztof.kozlowski@canonical.com>
Hi!
> rtc01 fails on missed alarm on multiple different Azure instances if the
> alarm is set for the next minute:
>
> rtc01 0 TINFO : RTC READ TEST:
> rtc01 1 TPASS : RTC READ TEST Passed
> rtc01 0 TINFO : Current RTC date/time is 11-6-2021, 09:00:58.
> rtc01 0 TINFO : RTC ALARM TEST :
> rtc01 0 TINFO : Alarm time set to 09:01:03.
> rtc01 0 TINFO : Waiting 5 seconds for the alarm...
> rtc01 2 TFAIL : rtc01.c:151: Timed out waiting for the alarm
>
> Reproduced easily with rtcwake:
>
> $ rtcwake -d rtc0 -m on -s 50 -v
>
> 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.
I do not think that adding workarounds for a broken platforms into
testcases is a right thing to do.
--
Cyril Hrubis
chrubis@suse.cz
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/2] rtc01: add workaround for broken CMOS RTC on Microsoft Hyper-V cloud
Date: Fri, 10 Sep 2021 10:34:48 +0200 [thread overview]
Message-ID: <YTsYqBJP8oWiuEGQ@yuki> (raw)
Message-ID: <20210910083448.iOh5QWBbFFXD3SctbysNjTJ2StCNtqmbsmvIgihlyQA@z> (raw)
In-Reply-To: <20210909163326.42598-2-krzysztof.kozlowski@canonical.com>
Hi!
> rtc01 fails on missed alarm on multiple different Azure instances if the
> alarm is set for the next minute:
>
> rtc01 0 TINFO : RTC READ TEST:
> rtc01 1 TPASS : RTC READ TEST Passed
> rtc01 0 TINFO : Current RTC date/time is 11-6-2021, 09:00:58.
> rtc01 0 TINFO : RTC ALARM TEST :
> rtc01 0 TINFO : Alarm time set to 09:01:03.
> rtc01 0 TINFO : Waiting 5 seconds for the alarm...
> rtc01 2 TFAIL : rtc01.c:151: Timed out waiting for the alarm
>
> Reproduced easily with rtcwake:
>
> $ rtcwake -d rtc0 -m on -s 50 -v
>
> 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.
I do not think that adding workarounds for a broken platforms into
testcases is a right thing to do.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-09-10 8:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 16:33 [LTP] [PATCH 1/2] rtc01: add space to beginning of comments Krzysztof Kozlowski
2021-09-09 16:33 ` Krzysztof Kozlowski
2021-09-09 16:33 ` [LTP] [PATCH 2/2] rtc01: add workaround for broken CMOS RTC on Microsoft Hyper-V cloud Krzysztof Kozlowski
2021-09-09 16:33 ` Krzysztof Kozlowski
2021-09-10 8:34 ` Cyril Hrubis [this message]
2021-09-10 8:34 ` Cyril Hrubis
2021-09-10 8:35 ` Krzysztof Kozlowski
2021-09-10 8:35 ` Krzysztof Kozlowski
2021-09-10 11:03 ` Thadeu Lima de Souza Cascardo
2021-09-10 11:03 ` Thadeu Lima de Souza Cascardo
2021-09-10 9:14 ` [LTP] [PATCH 1/2] rtc01: add space to beginning of comments Cyril Hrubis
2021-09-10 9:14 ` Cyril Hrubis
2021-09-10 12:46 ` Krzysztof Kozlowski
2021-09-10 12:46 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YTsYqBJP8oWiuEGQ@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox