<!DOCTYPE html>
<html><head>
<meta charset="UTF-8">
</head><body><p><br></p><p>Gentlemen,</p><p><br></p><blockquote type="cite"><p>On September 28, 2016 at 4:21 PM "Eric S. Raymond" <esr@thyrsus.com> wrote:<br><br><br><br>The big deal is that a build *with* KERNEL_PLL will generate adjtimex(2)<br>events into the capture logs. A build without KERNEL_PLL won't. Neither<br>kind of log will be replayable on the other kind of build.<br><br>The original goal for TESTFRAME was to be able to collect a bunch<br>of representative capture logs and reply them on every waf check,<br>and along with the unit tests at the end of the build.<br><br>The problem is that KERNEL_PLL as a build *variable* makes capture<br>logs non-portable, which means we can't have a single set of standard<br>tests. I have known this was going to be a problem for a long time -<br>I've mumbled about it once or twice. I kept hoping I'd find a<br>solution. I didn't.<br><br></p></blockquote><p>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?<br></p><p><br></p><p> - John D. Bell</p></body></html>