Gentlemen,
On September 28, 2016 at 4:21 PM "Eric S. Raymond" <[email protected]> wrote:
The big deal is that a build *with* KERNEL_PLL will generate adjtimex(2)
events into the capture logs. A build without KERNEL_PLL won't. Neither
kind of log will be replayable on the other kind of build.
The original goal for TESTFRAME was to be able to collect a bunch
of representative capture logs and reply them on every waf check,
and along with the unit tests at the end of the build.
The problem is that KERNEL_PLL as a build *variable* makes capture
logs non-portable, which means we can't have a single set of standard
tests. I have known this was going to be a problem for a long time -
I've mumbled about it once or twice. I kept hoping I'd find a
solution. I didn't.
At the risk of sounding stupid (or at least uninformed), couldn't you capture TESTFRAME logs from the same hardware *booted on each kind of kernel* (with the kernels being otherwise identically configured), and just have the "WITH" and "WITHOUT" sets of tests to run? Yes, doubled workload; is that a show-stopper? Can we scrounge up enough testing environments without having to reboot any individual box?
- John D. Bell
_______________________________________________ devel mailing list [email protected] http://lists.ntpsec.org/mailman/listinfo/devel
