Issue metadata
Sign in to add a comment
|
29.4% regression in indexeddb_perf at 429958:430101 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 10 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8996425522989419072
,
Nov 10 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@429957 6114.8 974.229 18 good chromium@430101 5662.42 165.76 18 bad Bisect job ran on: mac_hdd_perf_bisect Bug ID: 663957 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests indexeddb_perf Test Metric: Total Perf/Total Perf Relative Change: 5.59% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/875 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8996425522989419072 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5269524004208640 | 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!
,
Feb 3 2017
These regressions happened before M56 branch. M56 is now in stable. These regressions made it to the stable channel. Marking wontfix. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by rsch...@chromium.org
, Nov 10 2016