Fix for default test config file

[yennster]

Description

Fixes #5543

This change allows for mbed test to build with an mbed_app.json file by default if one exists in the project's root directory (i.e. for running the ci-test-shield tests). However, if the mbed_app.json file is not in the root directory, then it's location needs to be specified in the command with the --app-config parameter.

Steps to test or reproduce

Before fix:
If you run the ci-test-shield tests with mbed test -t GCC_ARM -m NUCLEO_F207ZG -n tests* --compile without a specified --app-config you get the following errors related to the unspecified mbed_app.json:

        [Error] Mixed.cpp@68,22: 'MBED_CONF_APP_I2C_SDA' was not declared in this scope
        [Error] Mixed.cpp@68,44: 'MBED_CONF_APP_I2C_SCL' was not declared in this scope
        [Error] Mixed.cpp@68,66: 'MBED_CONF_APP_I2C_EEPROM_ADDR' was not declared in this scope
        ...

After fix:
If you run the ci-test-shield tests with mbed test -t GCC_ARM -m NUCLEO_F207ZG -n tests* --compile without a specified --app-config, if there exists an mbed_app.json in the root directory of the project then the tests compile and run successfully.

[yennster]

@sarahmarshy @geky related to #5543

[0xc0170]

@jeromecoutant Does this fix the issue you reported?

[0xc0170]

/morph build

[mbed-ci]

Build : FAILURE

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

[jeromecoutant]

Hi
Yes, issue #5543 can be closed with that patch
Thx

[0xc0170]

Building fails, please review the latest results

[yennster]

Fixed with help from @theotherjimmy
@0xc0170

[jeromecoutant]

Quick tests with the last version:

• OK in mbed-os environment
• OK in ci-shield environment

Thx Jenny

[jeromecoutant]

Minor question about the TODO comment https://github.com/yennster/mbed-os/blob/b3ba9a55b900058c3317f707bc867c91ff70fb84/tools/test.py#L141

Is this patch correcting it ?

[theotherjimmy]

@jeromecoutant This patch does not touch that code or remove that comment. No, it does not correct that TODO.

[0xc0170]

/morph build

[0xc0170]

@theotherjimmy Are you happy with this patch?

[theotherjimmy]

@0xc0170 The last commit is mine :P

[yennster]

@sarahmarshy

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[mbed-ci]

Test : SUCCESS

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

[mbed-ci]

Exporter Build : FAILURE

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

[theotherjimmy]

@kegilbert That export failure is not showing any failed exports. Could you take a look?

[kegilbert]

@theotherjimmy Looks like a node went down midrun on one of the boards, rekicking off.
/morph export-build

[mbed-ci]

Exporter Build : SUCCESS

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