kc3-lang/libevent/test/tinytest.c
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
207ea62b | 2023-02-12 16:46:40 | test: handle -v as --verbose for regress | |
 |
3daebf30 | 2021-09-29 13:50:35 | test: retriable tests are marked failed only when all attempts have failed Signed-off-by: Thomas Perrot <thomas.perrot@bootlin.com> | |
|
90846c30 | 2021-09-19 13:18:40 | test: add --retries-delay (and set to 1 second by default) In attemp to address failures of dns/tcp_* tests under windows [1]. [1]: https://github.com/azat/libevent/runs/3644218468?check_suite_focus=true | |
|
d7d6af75 | 2021-09-19 13:15:02 | test: add --retries argument | |
|
6754740f | 2020-06-25 21:01:53 | test: detect test failures if atexit handler calls _exit(!0) (sanitizers) tinytest uses another way of detecting test failures, it uses pipe between child and parent, and if the test function in child returns OK it writes OK flag into pipe, and reads it in parent. However sanitizers uses atexit handlers to detect leaks, and this will not detect failures in case of exit() will be called from the atexit handlers, fix this by checking status after waitpid(). | |
 |
8d5c5650 | 2019-09-26 21:47:51 | tinytest: support timeout on Windows | |
|
8a674243 | 2019-03-24 20:36:16 | tinytest: fix parsing --timeout argument Fixes: 15b2f41d ("tinytest: implement per-test timeout (via alarm() under !win32 only)") | |
|
15b2f41d | 2019-03-24 16:44:56 | tinytest: implement per-test timeout (via alarm() under !win32 only) | |
 |
63b065be | 2018-11-20 01:06:04 | regress: introduce TT_RETRIABLE We have some tests that has false-positive due to real/CPU time bound, but they are pretty generic and we do not want to skip them by default. TT_RETRIABLE is the flag that will indicate tinytest to retry the test in case of failure, use it to avoid next possible false-positives: - real time-related - CPU time-related Since I guess it is better to see/grepping RETRYING messages over ignoring completely failed builds. No configuration switch for number of retries was done on purpose (only 3 retries and no more). And this is how it looks BTW: $ gcc ../test/tinytest_demo.c ../test/tinytest.c $ ./a.out --verbose --no-fork demo/timeout_retry demo/timeout_retry: FAIL ../test/tinytest_demo.c:201: assert(i != 1): 1 vs 1 [timeout_retry FAILED] [RETRYING timeout_retry (3)] demo/timeout_retry: OK ../test/tinytest_demo.c:201: assert(i != 1): 2 vs 1 OK ../test/tinytest_demo.c:213: assert(t2-t1 >= 4): 5 vs 4 OK ../test/tinytest_demo.c:215: assert(t2-t1 <= 6): 5 vs 6 1 tests ok. (0 skipped) | |
 |
7a804767 | 2014-03-06 18:09:00 | Update to the latest version of tinytest This brings us up to tinytest 709a36ba63ff16d8 |