Skip flaky test when not moving into anticipated forever pending sync state #1872
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
Signed-off-by: Sunik Kupfer <[email protected]>
sunkup
changed the title
sunkup
changed the title
Signed-off-by: Sunik Kupfer <[email protected]>
rfc2822
approved these changes
Dec 9, 2025
sunkup
deleted the
1835-accountsettingsmigration21testtestcancelssyncandclearspendingstate-sometimes-fails
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Purpose
Sometimes we don't manage to move into the forever pending sync state. In those cases the test should be skipped.
Short description
Check using
Assume.assumeTrue(instead of assert) that we have moved into the forever pending sync state. If not then the test will be skipped.Checklist