Improve output on Clock Jitter test failure
Bug #1900448 reported by
Jeff Lane
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox Provider - Base |
Fix Released
|
Medium
|
Jeff Lane |
Bug Description
When the jitter test fails, the output can be a bit unfriendly:
Testing for clock jitter on 96 cpus
ERROR, jitter = 0.288711
iter = 2549, cpus = 0,95
FAILED: 1 iterations failed
This could stand some improvements.
Related branches
~bladernr/plainbox-provider-checkbox:1900448-improve-jitter-test-output
- Jonathan Cave (community): Approve
-
Diff: 15 lines (+2/-2)1 file modifiedsrc/clocktest.c (+2/-2)
Changed in plainbox-provider-checkbox: | |
status: | In Progress → Fix Committed |
Changed in plainbox-provider-checkbox: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Updated output is a little more informative:
$ ./clocktest
Testing for clock jitter on 8 cpus
ERROR: jitter = 0.010292 Jitter must be < 0.2 to pass
ERROR: Failed Iteration = 72, Slowest CPU: 0 Fastest CPU: 7
FAILED: 1 iterations failed