Issue metadata
Sign in to add a comment
|
10.2% regression in blink_perf.layout at 431450:431483 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 16 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8995810221066544384
,
Nov 17 2016
===== BISECT JOB RESULTS ===== Status: failed ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@431449 772.795 74.9778 25 good chromium@431466 856.386 69.8719 25 bad chromium@431483 860.281 73.2842 25 bad Bisect job ran on: android_nexus6_perf_bisect Bug ID: 666006 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.layout Test Metric: layers_overlap_2d/layers_overlap_2d Relative Change: 11.32% Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2760 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995810221066544384 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=6439949954449408 | 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!
,
Nov 17 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8995783957444938320
,
Nov 17 2016
===== BISECT JOB RESULTS ===== Status: failed ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@431449 773.166 60.3418 25 good chromium@431466 850.154 67.7524 25 bad chromium@431483 853.813 69.3772 25 bad Bisect job ran on: android_nexus6_perf_bisect Bug ID: 666006 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.layout Test Metric: layers_overlap_2d/layers_overlap_2d Relative Change: 10.43% Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2763 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995783957444938320 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5239200578797568 | 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!
,
Nov 17 2016
Both bisects timed out after a test ran with no output for an hour. This is bug 664765.
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982651501968955024
,
Jul 27 2017
This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by jessimb@chromium.org
, Nov 16 2016