Issue metadata
Sign in to add a comment
|
36.7% regression in page_cycler_v2.tough_layout_cases at 437396:437467 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 12 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8993472719849337872
,
Dec 12 2016
+simonhatch, dtu: I get the error "Builder android_webview_aosp_perf_bisect not found". Was it recently changed to "webview_arm64_aosp_perf_bisect"?
,
Dec 12 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@437395 163.39 192.417 21 good chromium@437467 163.005 86.9296 21 bad Bisect job ran on: winx64intel_perf_bisect Bug ID: 673327 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...picarisimo.es page_cycler_v2.tough_layout_cases Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-warm/http___picarisimo.es Relative Change: 0.24% Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/1250 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993472719849337872 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5779967118409728 | 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!
,
Dec 12 2016
Where are you seeing this error? It looks like that bot was renamed android_webview_aosp_perf_bisect -> android_webview_arm64_aosp_perf_bisect back in June: https://codereview.chromium.org/2088033002/
,
Dec 12 2016
Whoops, pasted this on the wrong bug, was comparing this "successful" output with an unsuccessful one at bug 673325. Sorry for the confusing comment! Will move that discussion to bug 673325.
,
Dec 16 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8993113859376471888
,
Dec 16 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@437395 149.45 105.063 21 good chromium@437467 168.785 114.669 21 bad Bisect job ran on: winx64intel_perf_bisect Bug ID: 673327 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...picarisimo.es page_cycler_v2.tough_layout_cases Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-warm/http___picarisimo.es Relative Change: 12.94% Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/1258 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993113859376471888 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5771600304013312 | 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!
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982607789195838096
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982592573475459888
,
Jul 27 2017
This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by pmeenan@chromium.org
, Dec 12 2016