subsys/zbus: benchmark test runs "too fast" with picolibc #53589
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When using picolibc, this benchmark completes faster than the timer tick interval on several qemu instances. Instead of failing the test, pretend it finished in 1 millisecond. Signed-off-by: Keith Packard <[email protected]>
|
Hi Keith, could you please try #53563 and let me know what you think (and your findings)? |
|
Superseded by #53684 which increases the system tick so that qemu_nios2 has enough clock resolution to measure performance here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When using picolibc, this benchmark completes faster than the timer tick interval on several qemu instances. Instead of failing the test, pretend it finished in 1 millisecond.
Signed-off-by: Keith Packard [email protected]