On Wed, 2020-04-15 at 11:05 -0600, Geoffrey Marr wrote:
That makes sense, using something that will almost certainly be in
use in
any system we ever launch (for the foreseeable future). I would, however,
counter with chrony being a similar service that will most likely be in use
for a long time in all of our systems and is likely to be fixed very
quickly, should it ever have a problem. At this point, switching to chrony
as the default service here would solve this problem and be ubiquitous
across all our platforms.
What don't you support? Creating a separate test case specific to systems
tested via remote login, or keeping one singular testcase across all
platforms?
Creating a separate test case.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net