[DNM] Silly change to test CI

[cmonr]

Description

CI is having an unusually high false failure rate. Need to definitively determine if master is ok.

Pull request type

[x] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

[cmonr]

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

/morph test
/morph export-build
/morph mbed2-build

[mbed-ci]

Exporter Build : SUCCESS

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

[studavekar]

@cmonr how can we test stability? We have seen failure in past #8333 , #8320 . https://jira.arm.com/browse/IOTMORF-2289 due to test instability.

[mbed-ci]

Test : SUCCESS

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

[cmonr]

Network interface test re-enabled in CI. Local testing shows issue is no longer present.
/morph test

[cmonr]

#8731 (comment)

@studavekar The main thing I can think of at the moment is that we rerun tests multiple times, and see if anything comes up again.

The three tests that you mentioned are incredibly intermittent, and need to be stressed in certain ways to reproduce. I don't have an easy answer/solution to going about how to debug them.

[mbed-ci]

Test : SUCCESS

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

[cmonr]

Three to get ready:
/morph test

[mbed-ci]

Test : SUCCESS

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

[cmonr]

Closing this since it's served it's purpose.

It would appear that CI is back to normal.