Bug P1
Status Update
Comments
xi...@google.com <xi...@google.com> #2
Automatic regression verification started for measurement:
ChromiumPerf/android-pixel6-perf/system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:malloc:max_committed_size_avg/browse_news
Verification workflow id: projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/f430dab5-4642-48dd-a3d6-a50904c1d68e
ChromiumPerf/android-pixel6-perf/system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:malloc:max_committed_size_avg/browse_news
Verification workflow id: projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/f430dab5-4642-48dd-a3d6-a50904c1d68e
al...@google.com <al...@google.com> #3
🥪 Regression verification projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/f430dab5-4642-48dd-a3d6-a50904c1d68e job 169445e4610000 for test: ChromiumPerf/android-pixel6-perf/system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:malloc:max_committed_size_avg/browse_news
did NOT reproduce the regression with statistic: {'control_median': 135405568, 'lower': -2.0340368398504394, 'p_value': 0.42795460671186447, 'treatment_median': 135325696, 'upper': 1.0165479548803757}.
Issue closed.
did NOT reproduce the regression with statistic: {'control_median': 135405568, 'lower': -2.0340368398504394, 'p_value': 0.42795460671186447, 'treatment_median': 135325696, 'upper': 1.0165479548803757}.
Issue closed.
tn...@google.com <tn...@google.com> #4
al...@google.com <al...@google.com> #5
I'm asking the SysUI Notifications team, but I think we might not have an elegant solution that works outside of CTS.
al...@google.com <al...@google.com> #6
+cc Jeff on that team in case he has any ideas
Description
We do not allow
Thread.sleep()
in tests. The usage in protolayout tests is causing problems for other developers, and we will need to disable any tests relying onwaitForNotificationToDisappears
as a synchronization barrier.This bug is specifically for a fix, but you may also need to re-enable tests after you land one. The infrastructure team has asked developers blocked by tests that use this method to disable the relevant tests.