Issue metadata
Sign in to add a comment
|
2.9%-5% regression in page_cycler.intl_es_fr_pt-BR at 393201:393238 |
||||||||||||||||||
Issue descriptionFiling as a separate bug but it could also be related to crbug.com/611432
,
May 18 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@393200 2311.64 37.4904 12 good chromium@393238 2308.13 29.6907 12 bad Bisect job ran on: android_nexus9_perf_bisect Bug ID: 612841 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler.intl_ar_fa_he Test Metric: warm_times/page_load_time Relative Change: 0.35% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1798 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9012311370355059392 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5869867941494784 | 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
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 10 2016
Recovered on all tests. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by majidvp@chromium.org
, May 18 2016