tests-mbed_hal-sleep_manager: fix regression found on since PR #11721

[ABOSTM]

Description

Summary of change

tests-mbed_hal-sleep_manager is failed since merge of PR #11721 Bare metal greentea support
on many STM32 boards:
NUCLEO_F072RB, NUCLEO_F070RB
NUCLEO_F411RE, NUCLEO_F439ZI, NUCLEO_F446ZE, DISCO_F407VG
NUCLEO_F303RE
...

This PR solve the issue.

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

[] 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

Test PASSED on NUCLEO_F072RB and NUCLEO_F411RE

---

Reviewers

---

Release Notes

Summary of changes

Impact of changes

Migration actions required

[jeromecoutant]

Thx Alexandre

@rajkan01

[0xc0170]

I've checked nightly, this is there. Marked as 5.15

[0xc0170]

CI started

[evedon]

Thanks for fixing.

[mbed-ci]

Test run: FAILED

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

Failed test jobs:

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

[evedon]

Why was not this picked up in CI?

[0xc0170]

The failure above is with one device, needs restarting in ci (@ARMmbed/mbed-os-test already notified). Will restart once fixed

Why was not this picked up in CI?

I don't know, we need to find out. I've checked the PR tests and mbed_hal-sleep_manager was tested and passed. I've checked specifically nucleo f411.

[0xc0170]

CI restarted

[0xc0170]

I can see nightly started failing on Nov 14, only some platforms have sleep manager failures.

mbed-os-ci_greentea-test-nightly job 41 and above should have these failures