Andy Ross afbc044322 tests/kernel/thread_apis: Fix timing order ... This test understood that it can't demand equality in timing because of races against real time, so it simply validated that the test started at or later than the expected timeout expiration. But when calculating the expected time, it called k_uptime_ticks() AFTER the timeout was registered. So on systems with fast ticks (or just bad luck) a tick expiring between the two steps will look like an "early" expiration and fail the test. Do things in the proper order. Also, use the correct APIs for unit conversion and timeout construction. Signed-off-by: Andy Ross <andrew.j.ross@intel.com>		2021-03-08 18:15:53 -05:00
..
main.c	tests/kernel/thread_apis: Fix timing order	2021-03-08 18:15:53 -05:00
test_essential_thread.c	test: thread: add a test case for essential thread abort	2020-08-21 13:58:35 -04:00
test_kthread_for_each.c	test: thread_api: refine test coverage of thread_api	2021-03-02 14:28:24 -05:00
test_threads_cancel_abort.c	kernel: Remove abort and join implementation (UNBISECTABLE)	2021-02-24 16:39:15 -05:00
test_threads_cpu_mask.c	tests: threads: mark cpu_mask skipped where it does not run	2020-08-06 12:07:38 -05:00
test_threads_set_priority.c
test_threads_spawn.c	test: thread_api: refine test coverage of thread_api	2021-03-02 14:28:24 -05:00
test_threads_suspend_resume.c
tests_thread_apis.h