Issue metadata
Sign in to add a comment
|
32.7% regression in page_cycler_v2.intl_ar_fa_he at 434908:434955 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 2 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8994362874240798304
,
Dec 2 2016
===== BISECT JOB RESULTS ===== Status: failed === Bisection aborted === The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence. Please contact the the team (see below) if you believe this is in error. ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@434907 429.91 83.3428 27 good chromium@434955 431.229 105.576 27 bad Bisect job ran on: android_nexus6_perf_bisect Bug ID: 670795 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.masrawy.com. page_cycler_v2.intl_ar_fa_he Test Metric: timeToFirstContentfulPaint_avg/pcv1-cold/http___www.masrawy.com_ Relative Change: 0.31% Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2794 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994362874240798304 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5849221016584192 | 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 Tests>AutoBisect. Thank you!
,
Dec 4 2016
Bisect didn't reproduce; appears to have recovered now. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by qyears...@chromium.org
, Dec 2 2016