test: accept test result if RTC can't enable RTC_UIE_ON

The test might run on different platforms. If the platform happens
to have a RTC that does exist but unable to have RTC_UIE_ON set the
test will fail, while the chrony code is actually good.

Examples of bad clocks are:
- ppc64el: rtc-generic
- arm64: rtc-efi

To avoid that extend the log message check on 101-rtc to accept
that condition as a valid test result as well.

Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>

diff --git a/test/system/101-rtc b/test/system/101-rtc
index fa9a70d42e9908820f4c5e9a375c6f040dc02d34..68bce6809c8f5e318fc5b5d44ba2724b76285e83 100755 (executable)
--- a/test/system/101-rtc
+++ b/test/system/101-rtc
@@ -14,6 +14,6 @@ echo "1 $(date +%s) 0.0 0.0" > "$TEST_DIR/rtcfile"
 
 start_chronyd || test_fail
 stop_chronyd || test_fail
-check_chronyd_message_count "\(clock off from RTC\|RTC time before last\)" 1 1 || test_fail
+check_chronyd_message_count "\(clock off from RTC\|RTC time before last\|Could not \(enable\|disable\) RTC interrupt\)" 1 1 || test_fail
 
 test_pass