Issue metadata
Sign in to add a comment
|
16.3% regression in blink_perf.bindings at 409156:409165 |
||||||||||||||||||
Issue descriptionSee attached graph.
,
Aug 3 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005313740755883040
,
Aug 4 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@409155 163.641 4.86978 18 good chromium@409165 163.491 7.91387 18 bad Bisect job ran on: android_nexus5X_perf_bisect Bug ID: 634149 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.bindings Test Metric: undefined-first-child/undefined-first-child Relative Change: 1.04% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/431 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005313740755883040 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5871121992253440 | 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!
,
Sep 6 2016
Graph recovered in chromium revision range 409554 - 409593.
,
Sep 6 2016
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by aiolos@chromium.org
, Aug 3 2016