faraphel/chrony
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
chrony/test/system
History
Christian Ehrhardt c4d6f98bed 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>
2019-12-12 13:03:26 +01:00
..
001-minimal test: use env in shebang of system tests 2019-04-26 10:54:02 +02:00
002-extended test: use env in shebang of system tests 2019-04-26 10:54:02 +02:00
003-memlock test: use env in shebang of system tests 2019-04-26 10:54:02 +02:00
004-priority test: use env in shebang of system tests 2019-04-26 10:54:02 +02:00
005-scfilter test: use env in shebang of system tests 2019-04-26 10:54:02 +02:00
006-privdrop test: use env in shebang of system tests 2019-04-26 10:54:02 +02:00
007-cmdmon test: use env in shebang of system tests 2019-04-26 10:54:02 +02:00
100-clockupdate test: use env in shebang of system tests 2019-04-26 10:54:02 +02:00
101-rtc test: accept test result if RTC can't enable RTC_UIE_ON 2019-12-12 13:03:26 +01:00
102-hwtimestamp test: use env in shebang of system tests 2019-04-26 10:54:02 +02:00
103-refclock test: use env in shebang of system tests 2019-04-26 10:54:02 +02:00
104-systemdirs test: use env in shebang of system tests 2019-04-26 10:54:02 +02:00
run test: use env in shebang of system tests 2019-04-26 10:54:02 +02:00
test.common test: update log checks in system tests 2019-12-10 15:56:48 +01:00