Obsolete
Status Update
No update yet.
Comments
ch...@appspot.gserviceaccount.com
That fix has been cherry-picked into the release branch and will be available in the Fragment 1.5.1 release.
ch...@appspot.gserviceaccount.com
Alert group updated:
Added 1 regressions to the group
Internal (Googlers-only) Reports:
- Chromium:https://chrome-perf.corp.goog/u/?anomalyGroupID=9ab109a2-4f9e-44df-9e68-c885caab8ebb
(Legacy)https://chromeperf.appspot.com/group_report?group_id=9ab109a2-4f9e-44df-9e68-c885caab8ebb
Top 1 affected measurements in android-go-wembley-perf:
- system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/browse_news/browse_news_reddit_2019
11.66%: 68380540.0 -> 76354341.0 sizeInBytes
Added 1 regressions to the group
Internal (Googlers-only) Reports:
- Chromium:
(Legacy)
Top 1 affected measurements in android-go-wembley-perf:
- system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/browse_news/browse_news_reddit_2019
11.66%: 68380540.0 -> 76354341.0 sizeInBytes
ch...@appspot.gserviceaccount.com
🥪 Regression verification projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/5143feed-8ac2-461b-9b7e-e17a87c635ee job 1619fce2e10000 for test: ChromiumPerf/android-go-wembley-perf/system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:malloc:max_allocated_size_avg/browse_news
did NOT reproduce the regression with statistic: {'control_median': 40542400, 'lower': -1.2755748922659738, 'p_value': 0.28008678182959557, 'treatment_median': 40408760, 'upper': 0.39666308821093565}.
Issue closed.
did NOT reproduce the regression with statistic: {'control_median': 40542400, 'lower': -1.2755748922659738, 'p_value': 0.28008678182959557, 'treatment_median': 40408760, 'upper': 0.39666308821093565}.
Issue closed.
ch...@appspot.gserviceaccount.com
Reopened due to new regressions detected for this alert group:
Added 1 regressions to the group
Internal (Googlers-only) Reports:
- Chromium:https://chrome-perf.corp.goog/u/?anomalyGroupID=9ab109a2-4f9e-44df-9e68-c885caab8ebb
(Legacy)https://chromeperf.appspot.com/group_report?group_id=9ab109a2-4f9e-44df-9e68-c885caab8ebb
Top 1 affected measurements in android-go-wembley-perf:
- system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:malloc:max_committed_size_avg/browse_news
19.60%: 51908608.0 -> 62084561.0 sizeInBytes
Added 1 regressions to the group
Internal (Googlers-only) Reports:
- Chromium:
(Legacy)
Top 1 affected measurements in android-go-wembley-perf:
- system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:malloc:max_committed_size_avg/browse_news
19.60%: 51908608.0 -> 62084561.0 sizeInBytes
ch...@appspot.gserviceaccount.com
Automatic regression verification started for measurement:
ChromiumPerf/android-go-wembley-perf/system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:malloc:max_allocated_size_avg/browse_news
Verification workflow id: projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/145ab33a-c111-43e1-8336-6674f89d302e
ChromiumPerf/android-go-wembley-perf/system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:malloc:max_allocated_size_avg/browse_news
Verification workflow id: projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/145ab33a-c111-43e1-8336-6674f89d302e
ch...@appspot.gserviceaccount.com
🥪 Regression verification projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/145ab33a-c111-43e1-8336-6674f89d302e job 162ffce2e10000 for test: ChromiumPerf/android-go-wembley-perf/system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:malloc:max_allocated_size_avg/browse_news
did NOT reproduce the regression with statistic: {'control_median': 40396664, 'lower': -1.3295998145133603, 'p_value': 0.24702516570687294, 'treatment_median': 40165808, 'upper': 0.3072570634554017}.
Issue closed.
did NOT reproduce the regression with statistic: {'control_median': 40396664, 'lower': -1.3295998145133603, 'p_value': 0.24702516570687294, 'treatment_median': 40165808, 'upper': 0.3072570634554017}.
Issue closed.
Description
Internal (Googlers-only) Reports:
- Chromium:
(Legacy) Chromeperf Report:
Top 2 regressions (out of 2, with 0 improvements) in this group:
- ChromiumPerf/android-go-wembley-perf/system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:malloc:max_allocated_size_avg/browse_news
29.09%: 36595716.0 -> 47240941.0 sizeInBytes
- ChromiumPerf/android-go-wembley-perf/system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:java_heap:allocated_objects_size_avg/browse_news/browse_news_reddit_2019
16.70%: 8595526.5 -> 10030894.0 sizeInBytes
Top 2 affected measurements in android-go-wembley-perf:
- system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:malloc:max_allocated_size_avg/browse_news
29.09%: 36595716.0 -> 47240941.0 sizeInBytes
- system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:java_heap:allocated_objects_size_avg/browse_news/browse_news_reddit_2019
16.70%: 8595526.5 -> 10030894.0 sizeInBytes
Regressions grouped by system_health.memory_mobile includes data from the following benchmarks with listed owners:
system_health.memory_mobile: lizeb@chromium.org, pasko@chromium.org
Commits in this range:
Chromium Git Hash:
Chromium Commit Position:
V8 Commit Position:
WebRTC Git Hash: