Aaron Conole <acon...@redhat.com> writes: > The tests 'alarm_autotest' and 'cycles_autotest' rely on the underlying > system having very accurate and precise timing. On systems where the > timing isn't as rigid, or the load is particularly high, these tests are > unreliable since the wake latency from the scheduler can be high enough > to miss the timing window. > > Remove the timing related tests from the test suites. These tests now > ensure the add/remove callback infrastructure unit tests, but drop the > waits and reliance on system timing and load. > > This avoids FAIL on various testing infrastructures. > > Signed-off-by: Aaron Conole <acon...@redhat.com> > --- > v2: Drop the timing requirements, but keep the API calls
NAK - I have a v3 for this with some stuff that was missed.
