Draft
Conversation
pedro-psb
force-pushed
the
investigate-flaky-azure
branch
from
5fc9577 to
1893c77
Compare
A finalizer task (exclusive resource lock) can start before sibling tasks (shared resource lock) have completed if they are blocked on a separate exclusive resource. In the Redis worker, this bypasses FIFO ordering because the sibling's shared resource is never added to blocked_shared when the blocking reason is its exclusive resource. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
pedro-psb
force-pushed
the
investigate-flaky-azure
branch
from
1893c77 to
7abf5fb
Compare
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.
For now, this adds a minimum reproducer to the flaky azure replicate task.
It's seems like a redis worker bug on keeping the ordering (azure runs with the redis worker)
The newly added test failed every time on my machine.
🤖
A finalizer task (exclusive resource lock) can start before sibling tasks (shared resource lock) have completed if they are blocked on a separate exclusive resource. In the Redis worker, this bypasses FIFO ordering because the sibling's shared resource is never added to blocked_shared when the blocking reason is its exclusive resource.
📜 Checklist
See: Pull Request Walkthrough