Issue metadata
Sign in to add a comment
|
No data received for system_health.common_mobile from android-nexus5X since 480739 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 29 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975431406252844816
,
Jun 29 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.common_mobile Metric : scroll_animation:power_avg/browse_news/browse_news_reddit Revision Exit Code N chromium@480739 0 +- N/A 20 good chromium@480782 0 +- N/A 20 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.reddit system_health.common_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8975431406252844816 For feedback, file a bug with component Speed>Bisection
,
Jun 30 2017
,
Aug 21 2017
We've removed data stoppage regressions, triaging these through perfbot rotation now. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by tdres...@chromium.org
, Jun 29 2017