heap_and_stack test refactoring

[maciejbocianski]

Description

Test refactoring and alignment to coding standards
Added test for main stack

Status

READY

Migrations

NO

[maciejbocianski]

@bulislaw @0xc0170 @c1728p9
What do you think about memory layout test?
Maybe we should create separate test suite for memory layout?

[maciejbocianski]

After discussion with @bulislaw we decided to remove memory layout test and take care of it later

[bulislaw]

Yes, it's not good enough reason for us to ask partners (or do it ourselves) to update linker script for every platform for every compiler.

[0xc0170]

@maciejbocianski Feel free to close this. Not sure if good enough reason for an issue , as this can be turned into an issue to capture all problems you found with this patch.

[maciejbocianski]

@0xc0170 The problematic part of the test was removed.
Rest of the test is OK and ready to go
Please remove "do not merge" label

[bulislaw]

Lets ignore the memory layout tests for now, I'm not sure there's good enough reason to mandate that for existing platforms. At least the ones that are failing.

[maciejbocianski]

TODO comment added : add memory layout test.

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[mbed-ci]

Exporter Build : SUCCESS

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

[mbed-ci]

Test : FAILURE

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

[maciejbocianski]

@0xc0170
Fail is not connected to heap_and_stack test
Failing test: tests-netsocket-gethostbyname
Failing device: NUCLEO_F746ZG-IAR

[1511246558.84][HTST][INF] host test detected: default_auto 
[1511246620.47][CONN][RXD] :48::FAIL: Expected 0 Was -3010 
[1511246620.55][CONN][RXD] >>> failure with reason 'Assertion Failed' during 'Test Setup Handler'

[bulislaw]

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[mbed-ci]

Exporter Build : FAILURE

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

[mbed-ci]

Test : SUCCESS

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

[0xc0170]

An error has occurred. See the log file
/tmp/tmplo9Q1N/.metadata/.log.

SUCCESS
FAILURE

I can not see the failure and success at the same time. @maciejbocianski CAn you look at the log if you spot any error, its just one board and example blinky (not related but might be bug somewhere).

Retriggering at least once

/morph export-build

[maciejbocianski]

Don't know how to access log.
The error looks like totally not connected to this PR

[mbed-ci]

Exporter Build : SUCCESS

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