(BSR)[API] fix: potentially flaky test #15964
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
ogeber-pass
force-pushed
the
bsr/fix-flaky-test
branch
2 times, most recently
from
63c0c10 to
33a84a3
Compare
ogeber-pass
changed the title
|
Visit the preview URL for this PR (updated for commit 7e5f441): https://pc-pro-testing--pr15964-bsr-fix-flaky-test-lnhutq5y.web.app (expires Thu, 23 Jan 2025 17:03:34 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 032d233ee67e1c50d6af12e29c936c7076770eb1 |
ogeber-pass
had a problem deploying
to
pullrequest
GitHub Actions
Failure
ogeber-pass
force-pushed
the
bsr/fix-flaky-test
branch
from
33a84a3 to
17a5b35
Compare
ogeber-pass
force-pushed
the
bsr/fix-flaky-test
branch
from
17a5b35 to
7e5f441
Compare
xordoquy-pass
approved these changes
Jan 21, 2025
ogeber-pass
had a problem deploying
to
pullrequest
GitHub Actions
Failure
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.
In order to avoid flakiness, we order the result of the query