Moved ASYNCHRONOUS_DNS_SIMULTANEOUS_REPEAT under mbed extended tests

[mikaleppanen]

Description

Test is giving problems in some networks. Could be that DNS server is regarding repeated DNS enquiries on the test to be caused by malfunctioning device.

Pull request type

[X] Fix
[ ] Refactor
[ ] Target update
[ ] Feature
[ ] Breaking change

[adbridge]

How do we know that the asynchronous DNS tests will now be run? When are MBED_EXTENDED_TESTS actually run ?

[mikaleppanen]

@adbridge Tests flagged with MBED_EXTENDED_TESTS are build/run once a day against latest mbed-os master in the ip-core Jenkins build system.

[cmonr]

Thank you for the quick response!

[cmonr]

@adbridge Looks like there are some other tests already in the repo that use this compiler flag.

[cmonr]

/morph build

[adbridge]

@mikaleppanen So have we just effectively removed some testing from pull requests ? ie we won't now be able to detect issues with asynch dns until after a PR has been merged to master potentially ?

[mikaleppanen]

@adbridge The other asynchronous DNS tests will verify most of the functionality. So I think it is not problem if this particular test is not run for all pull requests.

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[mbed-ci]

Exporter Build : SUCCESS

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

[mbed-ci]

Test : FAILURE

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

[cmonr]

/morph test

[mbed-ci]

Test : SUCCESS

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