Define stack size of the threads spawned by RTOS threads test.

[pan-]

This stack size is adjusted for NRF51 and NRF52 based targets.
This should help: #2211

[pan-]

@sg- @geky Could you review this ?

[geky]

That looks good to me, although is there any reason to not use the explicit stack-size for every platform?

[pan-]

Yes, this test cause issues with IAR on NRF51 and NRF52.
With IAR the heap is fixed in the linker script (it can't be (AFAIK) RAM - other_sections_in_RAM).
In my case, the heap is fixed to a size comfortable size of 0x1800.
The default thread stack is set to 2048 bytes.

Just spawn 3 threads with a default stack size to blow up the system.

[geky]

Why not 512 for all platforms? Is there a reason to use DEFAULT_STACK_SIZE on other platforms?

[sg-]

@mbed-bot: TEST

HOST_OSES=windows
BUILD_TOOLCHAINS=GCC_ARM,ARM,IAR
TARGETS=K64F,NRF51_DK,NRF51_MICROBIT,NUCLEO_F411RE

[sg-]

/morph test

[mbed-bot]

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 519

Test failed!

[mbed-bot]

[Build ${MBED_BUILD_ID}]
FAILURE: Something went wrong when building and testing.

[sg-]

@mbed-bot: TEST

HOST_OSES=windows
BUILD_TOOLCHAINS=GCC_ARM
TARGETS=K64F,NRF51_DK,NRF51_MICROBIT,NUCLEO_F411RE

[mbed-bot]

[Build 702]
FAILURE: Something went wrong when building and testing.

[pan-]

@sg same as in #2247 the output is passing.
What is wrong with the build bot ?

[sg-]

What is wrong with the build bot ?

It was tired and needed a rest :)

[sg-]

/morph test

[sg-]

@mbed-bot: TEST

HOST_OSES=windows
BUILD_TOOLCHAINS=GCC_ARM,ARM,IAR
TARGETS=K64F,NRF51_DK,NRF51_MICROBIT,NUCLEO_F411RE

[mbed-bot]

[Build 716]
SUCCESS: Building succeeded and tests were run! Be sure to check the test results

[mbed-bot]

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 532

Test failed!