-
Notifications
You must be signed in to change notification settings - Fork 597
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
Changes in the Session Test App to verify Fireperf #no-changelog #6809
Conversation
📝 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 |
Test Results 38 files - 981 38 suites - 981 52s ⏱️ - 33m 14s Results for commit 4c5fe51. ± Comparison against base commit d2e72df. This pull request removes 5778 tests.
♻️ This comment has been updated with latest results. |
Size Report 1Affected Products
Test Logs |
The failing integration test seems to be flaky but it passed locally. Ignoring it for now.
|
Startup Time Report 1Note: Layout is sometimes suboptimal due to limited formatting support on GitHub. Please check this report on GCS. Notes
Startup Times
|
…-changelog (#6809) This change adds a way to repeatedly log identical performance traces in different processes. - Currently traces on different activities are logged on different Fireperf Sessions. - Adds additional logging to help identify different Firebase instances in different processes. - Adds Fireperf custom attributes to identify processes.
This change adds a way to repeatedly log identical performance traces in different processes.
I used this change to verify the behavior of duplicate traces in a single session. I've also used a manual UUID to simulate an identical session ID across two different processes.
no-changelog