Issue metadata
Sign in to add a comment
|
32.6%-163.6% regression in page_cycler_v2.intl_hi_ru at 450551:450659 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 17 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8987419830534286880
,
Feb 17 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_10_12_perf_bisect Benchmark : page_cycler_v2.intl_hi_ru Metric : timeToFirstContentfulPaint_avg/pcv1-warm/http___yandex.ru_yandsearch?lr_102567_text_%D0%9F%D0%BE%D0%B3%D0%BE%D0%B4%D0%B0 Revision Result N chromium@450572 48.979 +- 8.04227 21 good chromium@450659 49.1265 +- 12.0466 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...yandex.ru.yandsearch.lr.102567.text..D0.9F.D0.BE.D0.B3.D0.BE.D0.B4.D0.B0 page_cycler_v2.intl_hi_ru Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8987419830534286880 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6428866886762496 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Feb 17 2017
This appears to have recovered.
,
Mar 14 2017
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by alexclarke@chromium.org
, Feb 17 2017