Obsolete
Status Update
Comments
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #2
I just noticed that calling .showInfoWindow() on the marker DOES place it on top of the others.
Sadly I want no info window at all. For now the trick is to create a 0px * 0px view in my own InfoWindowAdapter.
Sadly I want no info window at all. For now the trick is to create a 0px * 0px view in my own InfoWindowAdapter.
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #3
🥪 Regression verification projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/aa32c317-c7aa-4115-89a5-88eef788d253 job 1444ab86610000 for test: ChromiumPerf/win-10_amd_laptop-perf/speedometer3/TodoMVC-Preact-Complex-DOM/Speedometer3
did NOT reproduce the regression with statistic: {'control_median': 22.520000000000074, 'lower': -2.039900804794059, 'p_value': 0.9838335812091827, 'treatment_median': 22.50500000000102, 'upper': 1.1063829786885915}.
Issue closed.
did NOT reproduce the regression with statistic: {'control_median': 22.520000000000074, 'lower': -2.039900804794059, 'p_value': 0.9838335812091827, 'treatment_median': 22.50500000000102, 'upper': 1.1063829786885915}.
Issue closed.
Description
Internal (Googlers-only) Reports:
- Chromium:
(Legacy) Chromeperf Report:
Top 1 regressions (out of 1, with 0 improvements) in this group:
- ChromiumPerf/win-10_amd_laptop-perf/speedometer3/TodoMVC-Preact-Complex-DOM/Speedometer3
10.84%: 22.380000000000003 -> 24.805 ms
Top 1 affected measurements in win-10_amd_laptop-perf:
- speedometer3/TodoMVC-Preact-Complex-DOM/Speedometer3
10.84%: 22.380000000000003 -> 24.805 ms
Regressions grouped by speedometer3 includes data from the following benchmarks with listed owners:
speedometer3: cbruni@chromium.org, vahl@chromium.org
Commits in this range:
Chromium Git Hash:
Chromium Commit Position:
V8 Commit Position:
WebRTC Git Hash: