Replace YieldingLock with ocs TimeoutLock #772
Merged
Conversation
This file contains 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
BrianJKoopman
force-pushed
the
koopman/replace-372-yieldinglock
branch
from
1ea4001 to
df462a8
Compare
BrianJKoopman
force-pushed
the
koopman/replace-372-yieldinglock
branch
from
df462a8 to
0566909
Compare
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.
Description
This removes the original
YieldingLockclass from the 372 agent. This was merged upstream asTimeoutLockinocs.Motivation and Context
Resolves #152.
How Has This Been Tested?
This was tested with a 372 at Yale. The
acq()process was left running while calling individual tasks that would cause an interaction with theTimeoutLock. Worked without issue.Types of changes
Checklist: