summaryrefslogtreecommitdiffstats
path: root/tests/timer/timer_test.ok
Commit message (Collapse)AuthorAgeFilesLines
* timer_test: set 8 as default steps, use the default in testsuite.atNeels Hofmeyr2016-09-221-14/+279
| | | | Change-Id: I5070578e9fe2bdacaad000eaafb8dc5f549d6f3e
* timer_test: print more details to stdout to checkNeels Hofmeyr2016-09-221-1/+98
| | | | | | | The test is now fully deterministic, so include all detail in stdout, to check for. Change-Id: Iecf6387f1d25253fcf1260777673853030c1d326
* timer_test: redirect some output from stderr to stdoutNeels Hofmeyr2016-09-221-0/+6
| | | | | | This way we can check the output in timer_test.ok. Change-Id: Ia3bba1c650be3558d370e0f59d4ee7f36ef97506
* timer_test: remove unused precision values and confusing logNeels Hofmeyr2016-09-221-1/+1
| | | | Change-Id: I1570b7096c757d63d23e0950feeeb7230f8a5c9f
* timer_test: also report early finishes, report timing on errorNeels Hofmeyr2016-09-221-1/+1
| | | | | | | | When a timer was late, show the timing details. Also count whether timers fired early, for completeness' sake. Change-Id: Id3942637d77a28b5092ffffcc3e6d9d67c2b8e68
* timer: Increase the imprecision we accept in this testHolger Hans Peter Freyther2012-04-051-1/+1
| | | | | | 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.
* tests: timer: use stderr for non-repeatable outputPablo Neira Ayuso2011-11-141-19/+2
| | | | | | | | 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.
* tests: Use GNU autotest to execute our tests and compare textual outputHolger Hans Peter Freyther2011-11-141-0/+19
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)