-
Notifications
You must be signed in to change notification settings - Fork 625
Add comments and asserts that didn't merge with PR 5059 #5063
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
Conversation
# Conflicts: # firebase-perf/src/main/java/com/google/firebase/perf/config/ConfigurationConstants.java
📝 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 |
Startup Time Report 1Note: Layout is sometimes suboptimal due to limited formatting support on GitHub. Please check this report on GCS. Startup time comparison between the CI merge commit (24ccc7c) and the base commit (dd04244) are not available. No macrobenchmark data found for the base commit (dd04244). Analysis for the CI merge commit (24ccc7c) can be found at: |
* Add different defaults for when RC fetch failed * Add changelog entry * Format * Add throttled case to isLastFetchFailed check * Add rc fetch failed defaults for cpu and memory capturing frequency * Address comments
Last commit didn't merge in #5059