-
Notifications
You must be signed in to change notification settings - Fork 2k
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
unittests/sht1x: decrease the amount of tested values on board #12054
unittests/sht1x: decrease the amount of tested values on board #12054
Conversation
Reduce the amount of tested values by a 100. This makes the testing time go from 3 minutes to 2 seconds on `frdm-kw41z`. Testing that the integer calculation matches the float one does not need to be performed on the full range on boards. Checking some values should be enough to detect overflow issues. The full range checking is kept on native.
I can verify that the unit tests now takes less than a second on the MSB-A2, instead of almost a minute. |
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.
ACK. Thanks for the fix!
It was easy when you explained what was done :) |
You should put "CI: run tests" and toggle "ci: ready for build" otherwise it will not execute the updated test. |
Thank you for the review! :) |
You're very welcome. Thanks for identifying and addressing the issue :-) |
Contribution description
Reduce the amount of tested values by a 100.
This makes the testing time go from 3 minutes to 2 seconds on
frdm-kw41z
.Testing that the integer calculation matches the float one does not need
to be performed on the full range on boards. Checking some values should
be enough to detect overflow issues.
The full range checking is kept on native.
Fixes #12042
Testing procedure
Running the
unittests
onfrdm-kw41z
now goes to the end of the test in time:I noticed the
RIOT kernel panic
, but this is also inmaster
On master the test was failing:
But when run with
term
we could get the output after 3:30 minutes (with theHARD FAULT
.Issues/PRs references
The test was failing during release too RIOT-OS/Release-Specs#128 (comment)