Make revcomp variation yield processor when spin-waiting #26701
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.
The valgrind executions of this test have been timing out with some frequency lately after some system upgrades in the spin version of the algorithm. I think that, to be correct, the spin versions need to be yielding the processor, and that historically we've "gotten away" with not doing so without penalty or overhead. Here, I'm updating the test to include the yield in hopes that it helps with the timeouts, and also to see what impact it has on the performance of the test.