46891f0213
These tests was written to try to eliminate timer interrupts, but the mechanism chosen (setting TICKS_PER_SECOND to 1) is dangerously susceptible to overflow conditions on systems with fast cycle counters and high timeout durations. Actually the tests pass just fine if you use a conventional tick rate and use a tickless-capable driver (which eliminates interrupts too, which is the whole point), but there's no easy way in kconfig to do an "if" to select that condition for capable systems only. Just disable tickless to keep the same behavior. Signed-off-by: Andy Ross <andrew.j.ross@intel.com> |
||
|---|---|---|
| .. | ||
| app_kernel | ||
| boot_time | ||
| footprint | ||
| latency_measure | ||
| object_footprint | ||
| sys_kernel | ||
| timing_info | ||