[ML] Increase tolerance for read/write lock test #1760
Merged
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
In elastic#1759 the tolerance on the read/write lock test had to be increased again due to a problem with sleep calls sleeping for longer than specified when running under Jenkins on macOS on ARM. The change was in the 2nd commit on elastic#1759. This change makes the same increase on the master branch, to keep the branches in sync.
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.
In #1759 the tolerance on the read/write lock test
had to be increased again due to a problem with sleep
calls sleeping for longer than specified when running
under Jenkins on macOS on ARM. The change was in the
2nd commit on #1759.
This change makes the same increase on the master
branch, to keep the branches in sync.