Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The
RtosTimer
test suite needs a fix/workaround for NRF51_DK board. As pointed out in this comment on #5323tests-mbedmicro-rtos-mbed-rtostimer
failed during ci-morph-test of a PR not related toRtosTimer
. I'm unable to reproduce this behaviour on my NRF51_DK locally, but have found several failed ci-morph-tests:They all fail on line 74, 115 or 232:
mbed-os/TESTS/mbedmicro-rtos-mbed/rtostimer/main.cpp
Lines 74 to 76 in 6912a9d
mbed-os/TESTS/mbedmicro-rtos-mbed/rtostimer/main.cpp
Lines 113 to 115 in 6912a9d
mbed-os/TESTS/mbedmicro-rtos-mbed/rtostimer/main.cpp
Lines 230 to 232 in 6912a9d
which means either
sem
is never released or there is a timing issue. Considering all failures happened on NRF51_DK target I assume a longer timeout is needed to prevent these random failures.I've pushed one additional commit with code cleanup.
Status
READY
cc @bulislaw @0xc0170