Issue metadata
Sign in to add a comment
|
1.4% regression in jetstream at 417948:418003 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 19 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9001073779765932288
,
Sep 19 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@417947 181.444 0.783823 18 good chromium@418003 181.778 0.808452 18 bad Bisect job ran on: win_perf_bisect Bug ID: 648293 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests jetstream Test Metric: Score/Score Relative Change: 0.33% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6940 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001073779765932288 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5813571349381120 | 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!
,
Oct 6 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999528969672368304
,
Oct 6 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@417947 181.667 0.485071 18 good chromium@418093 181.722 0.574513 18 bad Bisect job ran on: win_perf_bisect Bug ID: 648293 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests jetstream Test Metric: Score/Score Relative Change: 0.00% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6982 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999528969672368304 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5311952983687168 | 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!
,
Oct 6 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999514868443058576
,
Oct 6 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999514858262595024
,
Oct 7 2016
===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : [turbofan] Ship eval. Author : bmeurer Commit description: No longer disable TurboFan for functions with eval, but only disable Crankshaft in those cases. R=mstarzinger@chromium.org BUG=v8:5267 Review-Url: https://codereview.chromium.org/2334633002 Cr-Commit-Position: refs/heads/master@{#39338} Commit : f0a0c432a5d048d39f250a7bb20d662d14e1cd17 Date : Mon Sep 12 09:41:29 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@417924 183.2 0.447214 5 good chromium@417936 183.5 0.534522 8 good chromium@417939 183.0 0.0 8 good chromium@417940 183.125 0.834523 8 good chromium@417940,v8@f0a0c432a5 182.0 0.534522 8 bad <-- chromium@417940,v8@685d488288 181.625 0.744024 8 bad chromium@417941 181.6 0.547723 5 bad chromium@417942 182.0 0.707107 5 bad chromium@417947 181.6 0.894427 5 bad Bisect job ran on: win_perf_bisect Bug ID: 648293 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests jetstream Test Metric: Score/Score Relative Change: 0.87% Score: 99.5 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6984 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999514858262595024 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5856742875856896 | 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!
,
Oct 7 2016
===== BISECT JOB RESULTS ===== Status: failed ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@418003 181.333 0.887625 12 good chromium@418048 182.083 0.288675 12 bad chromium@418093 181.944 0.416176 18 bad Bisect job ran on: win_perf_bisect Bug ID: 648293 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests jetstream Test Metric: Score/Score Relative Change: 0.44% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6983 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999514868443058576 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5878998322642944 | 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 benjhayden@chromium.org
, Sep 19 2016