Issue metadata
Sign in to add a comment
|
23.6% regression in blink_perf.dom at 389084:389111 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 26 2016
===== BISECT JOB RESULTS ===== Status: completed ===== TESTED REVISIONS ===== Revision Mean Value Std. Dev. Num Values Good? chromium@389083 695.081917 16.347142 12 good chromium@389097 666.711333 17.358594 18 good chromium@389098 661.13925 17.251244 8 good chromium@389099 695.5656 14.158841 5 bad chromium@389101 684.429 14.17756 18 bad chromium@389104 696.912583 24.808401 12 bad chromium@389111 720.633375 22.390825 8 bad Bisect job ran on: android_nexus6_perf_bisect Bug ID: 606758 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.dom Test Metric: modify-element-id/modify-element-id Relative Change: 4.10% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2149 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9014314189275539824 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=6081037172473856 | 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!
,
Apr 28 2016
Test is too noisy |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by pmeenan@chromium.org
, Apr 26 2016