threads test adjust to run on devices with small RAM

[maciejbocianski]

Description

PR contains changes required to run test on NUCLEO_F070RB (16kB RAM) device
In the end we had to reduce thread number from 3 to 2 only in parallel thread tests which create child thread

After memory optimization for devices with 16kB RAM it was seen some problems with threads stack size on some boards (e.g NRF51_DK).
We decided to forfeit this test on devices with small RAM (e.g. NUCLEO_F070RB) and increase test threads stack size to make test working on other boards
See commit bc99556

Status

READY

Migrations

NO

Related PRs

#4890

[maciejbocianski]

it's less-invasive version of #4890
please review @bulislaw @c1728p9 @0xc0170 @jeromecoutant

[bulislaw]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 352
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5360/

Triggering tests

/morph test
/morph uvisor-test

[mbed-ci]

Test : FAILURE

Build number : 163
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/5360/163

[0xc0170]

nrf-51dk failures related to this change, please review them

[jeromecoutant]

Approved!

| NUCLEO_F070RB-GCC_ARM | NUCLEO_F070RB | tests-mbedmicro-rtos-mbed-threads | OK | 28.15 | default |
| NUCLEO_F072RB-GCC_ARM | NUCLEO_F072RB | tests-mbedmicro-rtos-mbed-threads | OK | 26.83 | default |

[maciejbocianski]

needs further memory optimization or test reduction if #5386 will not yield any additional free heap memory - working on it

[0xc0170]

@maciejbocianski Shall this be closed and opened once updated ?

[mbed-ci]

Build : SUCCESS

Build number : 535
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5360/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 150
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/5360/

[mbed-ci]

Test : FAILURE

Build number : 344
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/5360/344

[bulislaw]

@maciejbocianski please fix the issues with nrf51

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 573
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5360/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

[maciejbocianski]

@bulislaw @0xc0170 fix for NRF51_DK was added see PR description

[mbed-ci]

Test : SUCCESS

Build number : 390
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/5360/390

[mbed-ci]

Exporter Build : FAILURE

Build number : 187
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/5360/

[0xc0170]

@theotherjimmy @studavekar Can you investigate the latest failure above? I've seen it this week already, build is OK but later it fails during termination? and reports both success and failure. Attached below the log (only the last part of it):

Invoking: Cross ARM GNU Print Size
arm-none-eabi-size --format=berkeley "mbed-os-example-blinky.elf"
Invoking: Cross ARM GNU Create Flash Image
arm-none-eabi-objcopy -O binary "mbed-os-example-blinky.elf"  "mbed-os-example-blinky.bin"
   text	   data	    bss	    dec	    hex	filename
  58088	   2668	   6856	  67612	  1081c	mbed-os-example-blinky.elf
Finished building: mbed-os-example-blinky.bin
Finished building: mbed-os-example-blinky.siz
 
 

15:46:38 Build Finished (took 35s.116ms)


==========STDERR==========
Eclipse:
JVM terminated. Exit code=1
/usr/bin/java
-Dosgi.requiredJavaVersion=1.8
-XX:+UseG1GC
-XX:+UseStringDeduplication
-Dosgi.requiredJavaVersion=1.8
-Xms256m
-Xmx1024m
-jar /usr/local/eclipse//plugins/org.eclipse.equinox.launcher_1.3.201.v20161025-1711.jar
-os linux
-ws gtk
-arch x86_64
-launcher /usr/local/eclipse/eclipse
-name Eclipse
--launcher.library /usr/local/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.401.v20161122-1740/eclipse_1618.so
-startup /usr/local/eclipse//plugins/org.eclipse.equinox.launcher_1.3.201.v20161025-1711.jar
--launcher.appendVmargs
-exitdata 298009
-product org.eclipse.epp.package.cpp.product
-application org.eclipse.cdt.managedbuilder.core.headlessbuild
-data /tmp/tmp2mVpkL
-import /builds/ws/exporter-build-matrix/187/WIZWIKI_W7500P_gnuarmeclipse/sources/examples/mbed-os-example-blinky
-cleanBuild mbed-os-example-blinky
-vm /usr/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.8
-XX:+UseG1GC
-XX:+UseStringDeduplication
-Dosgi.requiredJavaVersion=1.8
-Xms256m
-Xmx1024m
-jar /usr/local/eclipse//plugins/org.eclipse.equinox.launcher_1.3.201.v20161025-1711.jar 

SUCCESS
FAILURE

[0xc0170]

/morph export-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 200
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/5360/

[bulislaw]

@0xc0170 @theotherjimmy ping

[0xc0170]

@0xc0170 @theotherjimmy ping

Will be integrated during the sync today

[jeromecoutant]

Hi

Bad news with 5.6.6 version
Test is FAILED running case #11: 'Testing parallel threads with child'
[1512442049.35][CONN][RXD] Operator new out of memory

NUCLEO_F070RB-GCC_ARM | NUCLEO_F070RB | tests-mbedmicro-rtos-mbed-threads | Testing parallel threads with child | 0 | 0 | ERROR | 0.0 |
| NUCLEO_F072RB-GCC_ARM | NUCLEO_F072RB | tests-mbedmicro-rtos-mbed-threads | Testing parallel threads with child | 0 | 0 | ERROR | 0.0 |

[maciejbocianski]

we have two ways out:

• further test reduction (what will significantly reduce test scope)
• solving GCC malloc issue (malloc unexpected behaviour on GCC_ARM compiler #5386)

@bulislaw @0xc0170