refactor: deterministic queue execution #588
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
…istic-queue-execution
|
There is no feedback from me. Very clean and nice code refactoring. 👍 It's amazing. I will merge in. |
|
@chrisleekr Thank you. 👍 |
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
All symbol processing will be done sequentially in the queue.
Related Issue
#587
Motivation and Context
Sequential processing in the queue is more deterministic than symbol locking which can occur at any time and can interrupt current job unexpectedly.
How Has This Been Tested?
Tested by refactored tests where lock/unlock symbols is replaced by job queueing.
Screenshots (if appropriate):