-
Notifications
You must be signed in to change notification settings - Fork 627
Fix inaccurate activity screen metrics. #2736
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
Coverage ReportAffected SDKs
Test Logs
NotesHTML coverage reports can be produced locally with Head commit (b057f165) is created by Prow via merging commits: 011b65b 8af227e. |
Binary Size ReportAffected SDKs
Test Logs
NotesHead commit (b057f165) is created by Prow via merging commits: 011b65b 8af227e. |
firebase-perf/src/main/java/com/google/firebase/perf/application/AppStateMonitor.java
Show resolved
Hide resolved
/test check-changed |
/test macrobenchmark |
firebase-perf/src/main/java/com/google/firebase/perf/application/AppStateMonitor.java
Show resolved
Hide resolved
Macrobenchmark ReportAffected SDKsMeasurements are for head commit (5e9b2bf). Diffing against base commit (91681dd) is working in progress.
|
/test macrobenchmark |
@jeremyjiang-dev: The following test failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
This PR is to fix:
Summary of changes:
frameMetricsAggregator.remove(activity)
withframeMetricsAggregator.reset()
becauseremove
does not clean the frame metrics, causes frame metrics for each activity is added on top of the data for all previous pages.frameMetricsAggregator.remove(activity)
(see b/133827763). However, this check will return false even if hardware acceleration is turned on by default. Now, if an activity is not hardware accelerated, the metrics will just be 0.