-
Notifications
You must be signed in to change notification settings - Fork 3k
Timeout & LowPowerTimeout tests #5106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
TESTS/mbed_drivers/timeout/main.cpp
Outdated
sem->release(); | ||
} | ||
|
||
void timeout_inc_callback(volatile uint32_t *cnt) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
coding style alignment in this file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I fixed brace positions for function declarations.
5eb67d2
to
bddb14b
Compare
/morph test |
/morph test-nightly |
Result: ABORTEDYour command has finished executing! Here's what you wrote!
|
Result: ABORTEDYour command has finished executing! Here's what you wrote!
|
bddb14b
to
c111ed3
Compare
Case("Callback override (with attach_us)", test_override<AttachUSTester<LowPowerTimeout> >), | ||
|
||
Case("Multiple timeouts running in parallel (with attach)", test_multiple<AttachTester<LowPowerTimeout> >), | ||
Case("Multiple timeouts running in parallel (with attach_us)", test_multiple<AttachUSTester<LowPowerTimeout> >), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These two tests with multiple LowPowerTimeout
objects fail on K64F, NUCLEO_F070RB, NUCLEO_L476RG. Waiting for the outcome of #5150.
Case("Multiple timeouts running in parallel (with attach_us)", test_multiple<AttachUSTester<LowPowerTimeout> >), | ||
|
||
Case("Zero delay (with attach)", test_no_wait<AttachTester<LowPowerTimeout> >), | ||
Case("Zero delay (with attach_us)", test_no_wait<AttachUSTester<LowPowerTimeout> >), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These tests fail on NUCLEO_F070RB, NUCLEO_F429ZI and NUCLEO_L476RG -- issue #5159.
Thanks for the report, I'll label this as needs preceeding PR, and we need to wait for the fixes until this is made green |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about moving the tests to
TESTS/mbed_drivers/timeout/{lp_timeout,timeout}/
Also can we make all the tests common (and the same) unless there are some characteristic of the specific timeout that we test.
|
||
Case("Zero delay (with attach)", test_no_wait<AttachTester<LowPowerTimeout> >), | ||
Case("Zero delay (with attach_us)", test_no_wait<AttachUSTester<LowPowerTimeout> >), | ||
|
||
Case("500us LowPowerTimeout", lp_timeout_500us, greentea_failure_handler), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we make these tests common for both test suites?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I'll move these test cases to the header file.
@bulislaw That was my initial idea but as it turned out this would require changing test discovery procedure which now expects strictly defined dir structure Lines 2046 to 2050 in 373e6ab
|
ok, makes sense. |
@fkjagodzinski @bulislaw is this now ready ? |
@adbridge PR needs a minor update. Should be ready tomorrow. |
c111ed3
to
a0829ee
Compare
a0829ee
to
82f781c
Compare
Update:
Now all the boards that failed before, that is NCS36510, NRF51_DK and NRF52_DK, pass every test case! @bulislaw, @0xc0170 could you take alook and accept this PR again, please? No changes (apart that |
@fkjagodzinski we are very close to a code freeze for 5.8, only PR critical for 5.8 can be run on the CI till we freeze (hopefully tomorrow). Next week should look better, we'll run it then. |
@0xc0170 @bulislaw Could y'all take another look? It looks like this is ready to go again. @0xc0170 Does this still need the DNM label? @fkjagodzinski We can't start CI until we have at least one review OK the PR. |
/morph build |
Build : SUCCESSBuild number : 1381 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 1035 |
Test : FAILUREBuild number : 1164 |
Restarting, a device error /morph test |
Test : SUCCESSBuild number : 1172 |
Description
Added unit tests for timeout classes
Timeout
,LowPowerTimeout
.Status
READY
Preceding PR's needed:
TimerEvent tests #5046-- provides a fix for several boards failing to handle a delay of 0 us,MCUXpresso: Fix LPTimer issue when using multiple timeout objects #5347-- provides a fix for LowPowerTimeout: Inconsistent delay when using multilple timeout objects #5150,Issues to be resolved before merge:
STM32: lp_ticker_fire_interrupt: Event handler not called instantly when scheduled with past timestamp #5159NCS36510: Timeout: Inconsistent delay when using multilple timeout objects #5431Fire interrupt function broken for nrf5x targets #5284