tests: kernel: timer_behaviour shouldn't use fabs #83815
+3
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the timer_behavior test uses fabs.
Since the C library functions being used in the kernel is restricted in Rule A.4 in the Coding Standard
We should probably not use these functions in kernel tests either.
To reproduce
I am unsure if this is the "correctest" solution, but since it is simple and makes the test work in strictly more cases I think it should be fine?
There are tests FORCING minimal libc on similar kernel tests, possibly to uncover similar issues. Should I add it to this test as well?