selftests: ringbuffers: give time to ringbuffer consumer #86
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.
Depending on the hardware used in this test, the result was either error or success.
I put some prints and found that in the test with faster hardware, the loader, when trying to consume the rinbuffer, was already in an overflowed state.
Debugging with the infamous print:
The output of trace_pipe:
This way, I added a sleep between the syscall mmap calls, allowing the loader to breathe and be able to consume the ringbuffer before it fills up.
Fixes #85