[feature-wisun] Disable sleep on STM32F4 as an workaround for stability issues.

[teetak01]

Summary of changes

This workaround is related to Mbed OS issue
#12294

Documentation

---

Pull request type

[X] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

---

Test results

[X] No Tests required for this change (E.g docs only update)
[] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

---

Reviewers

@artokin @mikter @mikaleppanen @TuomoHautamaki @yogpan01

[ciarmcom]

@teetak01, thank you for your changes.
@yogpan01 @artokin @mikter @TuomoHautamaki @mikaleppanen @ARMmbed/mbed-os-maintainers please review.

[0xc0170]

CI started

[mbed-ci]

Test run: FAILED

Summary: 1 of 9 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

• jenkins-ci/mbed-os-ci_greentea-test

[0xc0170]

The results are expected, sleep for that target failed. If this is pushed to a feature branch, every test run needs to be checked if there are any other failures besides sleep.

[teetak01]

@0xc0170 is there simple way to disable that specific test (and add clear commit-trail) that it is being ignored? I am not very familiar with the greentea side.

[0xc0170]

@jamesbeyond What shall we do to exclude this tests for one platform for one branch? Please advise

[artokin]

Agreed with @0xc0170 to push this fix in now. Test will be fixed later.

[jeromecoutant]

I don't understand the issue,
but maybe you can only remove SLEEP feature in your local mbed_app.json ?

[0xc0170]

That would be better fix 👍

[jamesbeyond]

a proper way to turn off a feature would add "device_has_remove": [ "SLEEP" ] in https://github.com/ARMmbed/mbed-os/blob/master/targets/targets.json#L4292
Or for temporary turn off, would be like Jerome suggested, add the same option in mbed_apps.json

[jeromecoutant]

I definitively can't approve any change in targets.json file....

[jamesbeyond]

the underlying issue #12294 is currently under investigation, once that been resolved, hope this change would be reverted