Issue metadata
Sign in to add a comment
|
7.8%-25.3% regression in startup.warm.blank_page at 402511:402552 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 2 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@402526 208.509 0.724352 18 good chromium@402529 208.073 0.526978 18 bad Bisect job ran on: mac_retina_perf_bisect Bug ID: 625413 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests startup.warm.blank_page Test Metric: open_tabs_time/open_tabs_time Relative Change: 0.17% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1378 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9008224695485370848 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5907282085281792 | 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!
,
Jul 3 2016
===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : Clean up the RWHVMac to ui::Compositor interface Author : ccameron Commit description: Move the "ui::Compositor's relationship to RWHVMac" state machine into BrowserCompositorViewMac. Clarify the state by renaming states from Active / Suspended / Destroyed to HasAttachedCompositor / HasDetachedCompositor / HasNoCompositor Change the thumbnailer's copy requests to be intercepted by the BrowserCompositorViewMac, and thereby have the copy request keep the ui::Compositor attached (even if the RenderWidgetHostImpl is hidden). BUG= 623716 Review-Url: https://codereview.chromium.org/2093113003 Cr-Commit-Position: refs/heads/master@{#402541} Commit : 9e8481c2e211439771d0634043d2addf9fe7b4ec Date : Tue Jun 28 21:07:43 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@402526 209.768 0.44129 5 good chromium@402539 210.263 0.979711 5 good chromium@402540 210.453 0.212491 5 good chromium@402541 263.853 0.912669 5 bad <-- chromium@402543 262.326 0.541108 5 bad chromium@402546 262.421 1.1392 5 bad chromium@402552 262.695 0.555007 5 bad Bisect job ran on: mac_retina_perf_bisect Bug ID: 625413 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests startup.warm.blank_page Test Metric: open_tabs_time/open_tabs_time Relative Change: 25.23% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1379 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9008187454932022080 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5286269945380864 | 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 qyears...@chromium.org
, Jul 2 2016