-
Notifications
You must be signed in to change notification settings - Fork 572
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RemoteConfigComponentTest.java: fix flaky test #6291
base: main
Are you sure you want to change the base?
Conversation
…Subscriber_firebaseNamespace_callsSubscriptionHandler
📝 PRs merging into main branchOur main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released. |
Generated by 🚫 Danger |
Coverage Report 1Affected Products
Test Logs |
Unit Test Results 40 files + 32 40 suites +32 1m 27s ⏱️ +59s Results for commit 0292af5. ± Comparison against base commit da0eefa. This pull request removes 22 and adds 309 tests. Note that renamed tests count towards both.
|
Size Report 1Affected ProductsNo changes between base commit (da0eefa) and merge commit (23e21a0).Test Logs |
Startup Time Report 1Note: Layout is sometimes suboptimal due to limited formatting support on GitHub. Please check this report on GCS. Notes
Startup Times
|
The flaky test is: registerRolloutsStateSubscriber_firebaseNamespace_callsSubscriptionHandler
The flaky failure is due to a race condition, and the error looks like this: