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 94.3583 4.49251 18 good chromium@396534 93.4102 3.76962 18 bad Bisect job ran on: android_s5_perf_bisect Bug ID: 616523 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: 4.61% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/676 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9011037073639846528 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5806692495785984 | 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 1 2016
kouhei, fs: It looks like this benchmark has a long history of being bimodal. Is this a known issue?
,
Jun 2 2016
Not sure it's the test as such. I suspect this bot isn't quite behaving though. (Notice how the big jumps occur in the ref-curve too.)
,
Jun 2 2016
,
Jun 24 2016
Kicked off a new bisect
,
Jul 1 2016
The test has stabilized. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by briander...@chromium.org
, Jun 1 2016