I'm thinking of a minimal test to catch things like #863
Poking at the keyboard finds a missing return: ntpq> doflake 3.0 Flakiness must be a (positive) float less than 1.ntpq> ntpq> So extra credit for checking error conditions. Could we add a debug switch so it would crash on any error (or lack of error)? That would make it useful for CI testing. Or maybe make the return code be the number of errors? -- These are my opinions. I hate spam. _______________________________________________ devel mailing list [email protected] https://lists.ntpsec.org/mailman/listinfo/devel
