5c2731f27f
The test relies on the workq thread being in the system. It is possible for the workq to not be in the system even if CONFIG_SYSTEM_WORKQUEUE is enabled, if nothing makes references to the symbols in the object file, so we cannot rely on the kconfig option to know if the system workq thread is in the system or not. So, force it in. Change-Id: I1ae2613fbd32928b673fc4c74a9dc56502255763 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com> |
||
---|---|---|
.. | ||
test_arm_irq_vector_table | ||
test_context | ||
test_critical | ||
test_early_sleep | ||
test_errno | ||
test_events | ||
test_fifo | ||
test_fifo_priv | ||
test_fp_sharing | ||
test_ipm | ||
test_irq_offload | ||
test_libs | ||
test_lifo | ||
test_mail | ||
test_mail_priv | ||
test_map | ||
test_map_priv | ||
test_mem_safe | ||
test_mutex | ||
test_nano_work | ||
test_obj_tracing | ||
test_pend | ||
test_pipe | ||
test_pipe_priv | ||
test_pool | ||
test_sema | ||
test_sema_priv | ||
test_sleep | ||
test_stack/nanokernel | ||
test_stackprot | ||
test_static_idt | ||
test_task | ||
test_task_priv | ||
test_tickless/microkernel | ||
test_timer |