Issue metadata
Sign in to add a comment
|
11.6%-21.8% regression in blink_perf.shadow_dom at 520046:520369 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8961040309576787088
,
Dec 6 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: INFRA_FAILURE The bisect was able to narrow the range, you can try running with: good_revision: 65e949b09c49e1eb6b929caa2346913e1e50b733 bad_revision : 71a2e331ff5347ad0b4cdaa27f9b40e1fb23464c If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_one_perf_bisect Benchmark : blink_perf.shadow_dom Metric : v0-large-distribution-without-layout/v0-large-distribution-without-layout Revision Result N chromium@520047 34.8431 +- 1.093 7 good chromium@520068 42.8447 +- 1.73313 6 bad chromium@520088 42.2737 +- 0.746953 6 bad chromium@520129 42.0955 +- 2.04668 6 bad Please refer to the following doc on diagnosing blink_perf regressions: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md 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 blink_perf.shadow_dom More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8961040309576787088 For feedback, file a bug with component Speed>Bisection
,
Dec 6 2017
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/128eef64040000
,
Dec 6 2017
😿 Pinpoint job stopped with an error. https://pinpoint-dot-chromeperf.appspot.com/job/128eef64040000
,
Dec 6 2017
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14da66c4040000
,
Dec 7 2017
😿 Pinpoint job stopped with an error. https://pinpoint-dot-chromeperf.appspot.com/job/14da66c4040000
,
Jan 22 2018
This recovered. +dtu, simonhatch, FYI on the pinpoint errors. These are pretty old, but I assume they were addressed?
,
Jan 22 2018
Believe the first failed with https://github.com/catapult-project/catapult/issues/3921 which was fixed in December, and the 2nd is the gitiles issue that was fixed last week. Dave, is that right? |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Dec 5 2017