Laytan Laats 71929f737b add forced shutdown to new test runner ...

Currently, a Ctrl+c starts a graceful shutdown of the tests and runner.
Sometimes tests get stuck and this would never complete.

This simply adds an extra step, if Ctrl+c is given for the second time,
just `os.exit` right away.

2024-06-10 15:35:23 +02:00

..

events.odin

Refactor the test runner

2024-06-02 14:34:31 -04:00

logging.odin

Refactor the test runner

2024-06-02 14:34:31 -04:00

reporting.odin

Support ODIN_TEST_PROGRESS_WIDTH=0

2024-06-02 14:47:07 -04:00

runner.odin

add error message for unknown test log level

2024-06-07 15:13:09 +02:00

signal_handler_libc.odin

add forced shutdown to new test runner

2024-06-10 15:35:23 +02:00

signal_handler_other.odin

Be specific about platforms not implementing test runner signal handler

2024-06-02 14:54:31 -04:00

signal_handler.odin

Catch SIGILL, SIGFPE, SIGSEGV in the test runner

2024-06-02 14:54:31 -04:00

testing.odin

Support deterministic random seeding of tests

2024-06-02 14:47:07 -04:00