Issue metadata
Sign in to add a comment
|
4% regression in jetstream at 433786:433816 |
||||||||||||||||||||
Issue descriptionGraphs included below.
,
Nov 28 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8994716085630540224
,
Nov 28 2016
===== BISECT JOB RESULTS ===== Status: failed === Bisection aborted === The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence. Please contact the the team (see below) if you believe this is in error. ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@433844 197.75 3.24037 24 good chromium@433909 197.083 5.46199 24 bad Bisect job ran on: winx64nvidia_perf_bisect Bug ID: 669187 Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests jetstream Test Metric: Score/Score Relative Change: None Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1958 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994716085630540224 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5257509990825984 | 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 28 2016
I've maked the alert invalid. However, assigning to metric owners in case they know where to look for regressions in the range of CLs.
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982632404798515104
,
Apr 11 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64nvidia_perf_bisect Benchmark : jetstream Metric : Score/Score Revision Result N chromium@433844 197.19 +- 2.64875 21 good chromium@433909 196.81 +- 3.48238 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests jetstream Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982632404798515104 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5257509990825984 | 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 Speed>Bisection. Thank you!
,
Aug 16 2017
Looks like we couldn't track this down. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by benhenry@chromium.org
, Nov 28 2016