| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I5070578e9fe2bdacaad000eaafb8dc5f549d6f3e
|
|
|
|
|
|
|
| |
The test is now fully deterministic, so include all detail in stdout, to check
for.
Change-Id: Iecf6387f1d25253fcf1260777673853030c1d326
|
|
|
|
|
|
| |
This way we can check the output in timer_test.ok.
Change-Id: Ia3bba1c650be3558d370e0f59d4ee7f36ef97506
|
|
|
|
| |
Change-Id: I1570b7096c757d63d23e0950feeeb7230f8a5c9f
|
|
|
|
|
|
|
|
| |
When a timer was late, show the timing details.
Also count whether timers fired early, for completeness' sake.
Change-Id: Id3942637d77a28b5092ffffcc3e6d9d67c2b8e68
|
|
|
|
|
|
| |
On a loaded server we might not be able to reach 10ms precision
in the test configuration and this is not a high precision timer
anyway.
|
|
|
|
|
|
|
|
| |
This makes happy gnu-autotest for the timer test.
We may still may fail if we run the test on a very heavy loaded
system, but given the amount of timers that we using for the
automatic test (only 32), this seems very unlikely to me.
|
|
The output of make check is looking like this now:
Regression tests.
1: bits ok
2: msgfile ok
3: sms ok
4: smscb ok
5: timer FAILED (testsuite.at:38)
6: ussd FAILED (testsuite.at:44)
|