You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After commit f1f63dd (arm64: FPU context switch support), I am getting timeout in twister for tests/kernel/semaphore/semaphore/kernel.semaphore and tests/kernel/condvar/condvar_api/kernel.condvar.
The permission to use multiple_condvar is not granted to test
test_condvar_multiple_threads_wait_wake, which results in
bunch or permission error messages, and actually not testing
the conditional variables. This grants the permission to
the those conditional variables to the test threads. Also,
replace the k_yield() with k_msleep() to allow all created
threads time to run. A simply k_yield() might let a few to
run before the next batch of "waking" threads start to run,
resulting in some conditional variables not being initialized
but trying to wake.
Fixeszephyrproject-rtos#34777
Signed-off-by: Daniel Leung <daniel.leung@intel.com>
The permission to use multiple_condvar is not granted to test
test_condvar_multiple_threads_wait_wake, which results in
bunch or permission error messages, and actually not testing
the conditional variables. This grants the permission to
the those conditional variables to the test threads. Also,
replace the k_yield() with k_msleep() to allow all created
threads time to run. A simply k_yield() might let a few to
run before the next batch of "waking" threads start to run,
resulting in some conditional variables not being initialized
but trying to wake.
Fixes#34777
Signed-off-by: Daniel Leung <daniel.leung@intel.com>
After commit f1f63dd (
arm64: FPU context switch support
), I am getting timeout in twister fortests/kernel/semaphore/semaphore/kernel.semaphore
andtests/kernel/condvar/condvar_api/kernel.condvar
.The error from semaphore test:
The error from the condvar_api test:
These faults were not there on the commit just before f1f63dd.
The text was updated successfully, but these errors were encountered: