-
Notifications
You must be signed in to change notification settings - Fork 3k
LowPowerTimeout tests #5163
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
LowPowerTimeout tests #5163
Conversation
Case("Test callback override (with attach_us)", test_override<TimeoutAttachUSTester>), | ||
|
||
Case("Test multiple timeouts running in parallel (with attach)", test_multiple<TimeoutAttachTester>), | ||
Case("Test multiple timeouts running in parallel (with attach_us)", test_multiple<TimeoutAttachUSTester>), |
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("Test multiple timeouts running in parallel (with attach_us)", test_multiple<TimeoutAttachUSTester>), | ||
|
||
Case("Test zero delay (with attach)", test_no_wait<TimeoutAttachTester>), | ||
Case("Test zero delay (with attach_us)", test_no_wait<TimeoutAttachUSTester>), |
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.
Added unit tests for LowPowerTimeout API.
2b0b67f
to
5a158d6
Compare
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.
Does it make sense for this test suite and Timeout be identical just with different implementation used? Maybe we could even try not to duplicate the test functions but push them to a utility file, if that's feasible in our current testing approach.
Description
Added unit tests for
LowPowerTimeout
.Status
HOLD --
LowPowerTimeout
unit tests moved to #5106CC @bulislaw @0xc0170