Issue metadata
Sign in to add a comment
|
1%-21.9% regression in page_cycler_v2.intl_es_fr_pt-BR at 429284:429421 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 7 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8996610308933225056
,
Nov 8 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@429344 65.6769 1.52126 18 good chromium@429347 65.1956 0.789348 18 bad Bisect job ran on: winx64nvidia_perf_bisect Bug ID: 663115 Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests page_cycler_v2.intl_ja_zh Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___kakaku.com_ Relative Change: 1.26% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1948 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8996610308933225056 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=4988890706870272 | 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!
,
Nov 8 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8996524677789902576
,
Nov 8 2016
===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : Add crash keys to TaskQueueManager::ProcessTaskFromWorkQueue Author : alexclarke Commit description: We suspect a bad task closure is getting posted and would like to add crash keys to aid diagnosis. BUG=660427 Review-Url: https://codereview.chromium.org/2464853002 Cr-Commit-Position: refs/heads/master@{#429285} Commit : c08c078b27b353f4ab8de7deccfb862270b1ff2a Date : Wed Nov 02 15:49:06 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@429283 55.7896 4.00642 5 good chromium@429284 52.7764 0.594026 5 good chromium@429285 66.0876 2.21062 5 bad <-- chromium@429286 65.2358 1.2868 5 bad chromium@429288 65.38 0.717869 5 bad chromium@429292 65.1352 0.884833 5 bad chromium@429301 67.5606 1.81074 5 bad chromium@429318 65.3466 1.05936 5 bad chromium@429353 64.7154 0.983054 5 bad Bisect job ran on: winx64nvidia_perf_bisect Bug ID: 663115 Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...kakaku.com. page_cycler_v2.intl_ja_zh Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___kakaku.com_ Relative Change: 16.00% Score: 99.5 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1950 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8996524677789902576 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5796381669720064 | 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! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by briander...@chromium.org
, Nov 7 2016