test/pbkdf2: enlarge stdio rx buffer #17928
Merged
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.
Contribution description
The pbkdf2-test contains transfers of upto
67 byte (65+2)87 byte (64*8/6+1) (8/6 is BASE64) only limited by the speed of the serial connection.The default rx buffer is 64 bytes -> if uart irqs are tight enough the bytes are not taken fast enough from the buffer and some are lost -> test fails
the failing test can be seen by sometimes failing on the emulated microbit in murdock.
The large writes are defined by pbkdf2/tests/02-random.py
This enlarges the buffer to 2^7 (128) bytes
Testing procedure
read and exec that test; sadly one might have to do multiple execs of that test to see it fail without this PR
Issues/PRs references
split out from #17918 as it is not that related to murdock