Issue metadata
Sign in to add a comment
|
71%-507.8% regression in blink_perf.svg at 396500:396534 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 1 2016
===== BISECT JOB RESULTS ===== Status: completed === Bisection aborted === The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression. Please contact the the team (see below) if you believe this is in error. === Warnings === The following warnings were raised by the bisect job: * Bisect failed to reproduce the regression with enough confidence. ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@396499 540.79 14.7277 18 good chromium@396534 533.176 11.0466 18 bad Bisect job ran on: android_s5_perf_bisect Bug ID: 616524 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.svg Test Metric: FoodLeifLodahl/FoodLeifLodahl Relative Change: 3.17% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/677 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9011037070698322592 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5853558105178112 | 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!
,
Jun 2 2016
,
Jun 9 2016
Automatic message: All alerts recovered. Graphs: https://chromeperf.appspot.com/group_report?bug_id=616524
,
Jun 24 2016
===== BISECT JOB RESULTS ===== Status: completed === Bisection aborted === The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression. Please contact the the team (see below) if you believe this is in error. === Warnings === The following warnings were raised by the bisect job: * Bisect failed to reproduce the regression with enough confidence. ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@396499 54.6008 0.837374 18 good chromium@396534 54.2558 0.912957 18 bad Bisect job ran on: android_s5_perf_bisect Bug ID: 616524 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.svg Test Metric: AzLizardBenjiPark/AzLizardBenjiPark Relative Change: 0.62% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/739 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9008936711254980800 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5854006472081408 | 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! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by briander...@chromium.org
, Jun 1 2016