tests: kernel.condvar: child thread is not running

[zerosensei]

Describe the bug
The child thread is not actually running, main thread priority is -1, the two child threads have priorities 0 and 1, respectively.

#define PRIO_WAIT (CONFIG_ZTEST_THREAD_PRIORITY + 2)
#define PRIO_WAKE (CONFIG_ZTEST_THREAD_PRIORITY + 1)

void test_condvar_wait_forever_wake(void)
{
	woken = 1;
	timeout = K_TICKS_FOREVER;


	k_thread_create(&condvar_tid, stack_1, STACK_SIZE,
			condvar_wait_wake_task, &timeout, NULL, NULL,
			PRIO_WAIT, K_USER | K_INHERIT_PERMS, K_NO_WAIT);

	/* giving time for the condvar_wait_wake_task to execute */
	k_yield();

	k_thread_create(&condvar_wake_tid, condvar_wake_stack, STACK_SIZE,
			condvar_wake_task, &woken, NULL, NULL,
			PRIO_WAKE, K_USER | K_INHERIT_PERMS, K_MSEC(1));

	/* giving time for the condvar_wake_task
	 * and condvar_wait_wake_task to execute
	 */
	k_yield();

	k_thread_abort(&condvar_wake_tid);
	k_thread_abort(&condvar_tid);
}

So k_yield() does not cause the child thread to execute.

Environment (please complete the following information):

• OS: Windows
• Toolchain: Zephyr SDK
• Commit SHA or Version used: v2.7.0-ncs1

[nashif]

should not be high, this is exact code from the test and all relates to test code and no some incorrect behavior of the implementation.

[chen-png]

this is not related to k_yield, it is the issue of this test design.
k_yield is used to give cpu access to those threads whose priority is higher or equal to current thread, but in this case, those two threads' priority is lower than current thread, so they won't be executed at all, this is correct, however, this isolates the design purpose of this test, it never runs child threads to test k_condar_wait with forever.

we could replace k_yield by k_sleep if we really want to run this tests.