Skip to content

NUMAKER_PFM_M487: wait_ns test failing in nightly #10726

@0xc0170

Description

@0xc0170

Description

All toolchains affected

[1559264675.43][CONN][INF] found KV pair in stream: {{__testcase_name;Test: wait_ns - compare with us_timer 1s}}, queued...
[1559264675.53][CONN][RXD] >>> Running case #1: 'Test: wait_ns - compare with lp_timer 1s'...
[1559264675.53][CONN][INF] found KV pair in stream: {{__testcase_start;Test: wait_ns - compare with lp_timer 1s}}, queued...
mbedgt: :80::FAIL: Expected 1.200000 Was 4.211486
[1559264679.85][CONN][RXD] :80::FAIL: Expected 1.200000 Was 4.211486
[1559264679.85][CONN][INF] found KV pair in stream: {{__testcase_finish;Test: wait_ns - compare with lp_timer 1s;0;1}}, queued...
[1559264679.96][CONN][RXD] >>> 'Test: wait_ns - compare with lp_timer 1s': 0 passed, 1 failed with reason 'Assertion Failed'
[1559264679.96][CONN][RXD]
[1559264680.07][CONN][RXD] >>> Test cases: 0 passed, 1 failed with reason 'Assertion Failed'
[1559264680.07][CONN][RXD] >>> TESTS FAILED!

Logs can be found : http://mbed-os-ci.s3-website-eu-west-1.amazonaws.com/?prefix=jenkins-ci/ARMmbed/mbed-os/mbed-os-ci-nightly/artifacts/master/224/greentea-test-HAL-Core/78/FAIL/NUMAKER_PFM_M487/

I've noticed #10683, addressing it partly (no target implementation yet).

@ARMmbed/team-nuvoton

@kjbracey-arm this provides an answer how come our tests have not caught it - they did but not yet reported.

Issue request type

[ ] Question
[ ] Enhancement
[X] Bug

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions