tests-mbed_hal-rtc_time_conv randomly fails on CI

[mprse]

Description

Target: NRF52_DK
Toolchain : All

Test tests-mbed_hal-rtc_time_conv randomly fails on CI. This test sends lots of data between host and the device using UART and sometimes the transmission is broken.

It looks like the issue has been first time caught in PR #8292 and then after the PR has been merged, the test started to fail on CI.

Issue request type

[ ] Question
[ ] Enhancement
[X] Bug

[0xc0170]

It looks like the issue has been first time caught in PR #8292 and then after the PR has been merged, the test started to fail on CI.

@marcuschangarm Have you experienced any issue ?

@ARMmbed/mbed-os-hal Can you help reviewing this bug ?

[ciarmcom]

Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-150

[marcuschangarm]

• Our CI infrastructure doesn't support UART flow control.
• The NRF52 doesn't claim to support the RTC API.

[mprse]

Yes the RTC is disabled on NRF52_DK. If the RTC is not supported but lp ticker is available, then rtc API is available and is using lp timer. Mainly this is also not the case of this test. This test verifies functions which only supports RTC. These are the time conversion funcions which converts unix timestamp to date/time and vice versa. They do not perform hw operations and the test is executed for targets with and without RTC support.

The problem of this test is that it sends lots of data to the host. Host verifies if time conversion was valid. I think that changes provided by the mentioned PR have influence on uart transmission since the test was ok before this change has been added.

Maybe we could create a PR which reverts this change and run morph few times.

[marcuschangarm]

The PR fixes hardware flow control for the NRF52. But since we don't have hardware flow control on the CI the code is inert during morph test.

[NirSonnenschein]

Note: this is still happening:
http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/7309/3396
Any updates on this issue?

[ciarmcom]

@mprse thank you for raising this issue.Please take a look at the following comments:

Could you add some more detail to the description? A good description should be at least 25 words.
What target(s) are you using?
What toolchain(s) are you using?
What version of Mbed OS are you using (tag or sha)?
It would help if you could also specify the versions of any tools you are using?
How can we reproduce your issue?

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

[adbridge]

As this was last seen in 2018 and we have since migrated the CI to OSS I am going to close this.