test: some cases are failing with GCC_ARM only over TMPM066 (M0)

[soramame21]

Description

Following cases failed on TMPM066. those cases were not created on mbed-os-5.8.2 at all.
Those binaries built with ARM or IAR had passed with no error, but those binaries built with GCC_ARM got failed for memory allocation on each case.

• features-tests-filesystem-buffered_block_device
• features-tests-filesystem-heap_block_device
• features-tests-filesystem-mbr_block_device
• features-tests-filesystem-util_block_device
• tests-mbed_platform-error_handling

Question

Are those test cases really necessary for constrained M0 device with very limited RAM?

Type

[X] Question
[ ] Enhancement
[X] Bug

Tag

mbed-os-5.9.0-rc1

Toolchain

GCC_ARM

Build command (a example)

mbed test -m TMPM066 -t GCC_ARM -vv -n tests-mbed_platform-error_handling

error log

[1528175371.56][CONN][RXD] >>> Running case #3: 'Test error context capture'...
[1528175371.62][CONN][INF] found KV pair in stream: {{__testcase_start;Test error context capture}}, queued...
[1528175371.68][CONN][INF] found KV pair in stream: {{__testcase_finish;Test error context capture;1;0}}, queued...
[1528175371.73][CONN][RXD] >>> 'Test error context capture': 1 passed, 0 failed
[1528175371.73][CONN][RXD]
[1528175371.77][CONN][RXD] >>> Running case #4: 'Test error hook'...
[1528175371.82][CONN][INF] found KV pair in stream: {{__testcase_start;Test error hook}}, queued...
[1528175371.86][CONN][INF] found KV pair in stream: {{__testcase_finish;Test error hook;1;0}}, queued...
[1528175371.90][CONN][RXD] >>> 'Test error hook': 1 passed, 0 failed
[1528175371.91][CONN][RXD]
[1528175371.95][CONN][RXD] >>> Running case #5: 'Test error logging'...
[1528175372.00][CONN][INF] found KV pair in stream: {{__testcase_start;Test error logging}}, queued...
[1528175372.05][CONN][INF] found KV pair in stream: {{__testcase_finish;Test error logging;1;0}}, queued...
[1528175372.10][CONN][RXD] >>> 'Test error logging': 1 passed, 0 failed
[1528175372.10][CONN][RXD]
[1528175372.16][CONN][RXD] >>> Running case #6: 'Test error handling multi-threaded'...
[1528175372.22][CONN][RXD]
[1528175372.22][CONN][RXD]
[1528175372.22][CONN][INF] found KV pair in stream: {{__testcase_start;Test error handling multi-threaded}}, queued...
[1528175372.24][CONN][RXD] ++ MbedOS Error Info ++
[1528175372.30][CONN][RXD] Error Status: 0x8001011f Code: 287 Entity: 1
[1528175372.35][CONN][RXD] Error Message: Operator new[] out of memory
[1528175372.35][CONN][RXD]
[1528175372.37][CONN][RXD] Location: 0x30a3
[1528175372.38][CONN][RXD] Error Value: 0x200
[1528175372.48][CONN][RXD] Current Thread: Id: 0x200017f4 Entry: 0x3c79 StackSize: 0x1000 StackMem: 0x20001840 SP: 0x20002680
[1528175491.31][HTST][INF] test suite run finished after 120.78 sec...

[deepikabhavnani]

@SenRamakri - Error handling test is failing for few devices, in case of multi-thread test case, does it make sense to reduce the stack size (320) and thread count (3) for this test ?