Add functional test to cover conversion of scheduled speculative workflow task to normal #4364
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
alexshtin
force-pushed
the
feature/test-convert-scheduled-speculative-wt
branch
from
2a5875e to
194a79d
Compare
…flow task to normal
alexshtin
force-pushed
the
feature/test-convert-scheduled-speculative-wt
branch
from
194a79d to
f0f931d
Compare
mmcshane
approved these changes
May 19, 2023
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.
What changed?
Add functional test to cover conversion of scheduled speculative workflow task to normal.
Why?
If new events come after speculative WT was scheduled but not started, then speculative WT is converted to normal, and events are delivered together with update request messages.
How did you test it?
This PR.
Potential risks
No risks.
Is hotfix candidate?
No.