Repository navigation
harden ManyRecoveriesSpec - #5264
Merged
Aaronontheweb merged 2 commits intoSep 6, 2021
Merged
Aaronontheweb merged 2 commits into
Aaronontheweb merged 2 commits into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This spec can fail because on a low CPU count machine, such as the type that can be used by Azure DevOps, 3 blocked threads can also mean 3 blocked CPUs. I believe most Azure DevOps machines run using ~2 vCPU.
It's possible there could be a deeper underlying issue with the
DedicatedThreadPoolthat could cause this problem, but instead I tried to constrain themax-concurrent-recoveries=1to limit the number of blocked CPUs to less than 1.