c4d6f98bed
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>
19 lines
532 B
Bash
Executable file
19 lines
532 B
Bash
Executable file
#!/usr/bin/env bash
|
|
|
|
. ./test.common
|
|
|
|
check_chronyd_features RTC || test_skip "RTC support disabled"
|
|
[ -c "/dev/rtc" ] || test_skip "missing /dev/rtc"
|
|
|
|
test_start "real-time clock"
|
|
|
|
minimal_config=1
|
|
extra_chronyd_options="-s"
|
|
extra_chronyd_directives="rtcfile $TEST_DIR/rtcfile"
|
|
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\|Could not \(enable\|disable\) RTC interrupt\)" 1 1 || test_fail
|
|
|
|
test_pass
|