TC_osKernelSuspend_1 can fail

[CanastraRF]

I used this Validation on a STM32L476RG Nucleo Board.
After reset the core clock is only 4MHz (MSI).
Often TC_osKernelSuspend_1() failed on
ASSERT_TRUE (osKernelSuspend() == 50);
because the return value of osKernelSuspend is often 49.

Then I double the core clock to 8MHz and it works fine.
Please specify a minimum core clock or set a range of 49 to 50 for this test.

Similar in TC_MutexCheckTimeout()

[VladimirUmek]

Hi,

to keep tests simple the mentioned test (and others too) does rely that the code before assert will execute fast enough so that assert condition will be true. Therefore you are right, slow CPU clock could cause a missing tick.

I think it should be possible to slightly modify the test and still ensure that ASSERT_TRUE (osKernelSuspend() == 50) will be true even at slower clocks. I'll provide PR that will address this. I would still like to keep the exact value for the assert and would not modify the assert range.

Please report if there are any other test that fail besides TC_osKernelSuspend_1() and TC_MutexCheckTimeout()!

Many thanks for bringing this to our attention!