Issue metadata
Sign in to add a comment
|
20.3% regression in page_cycler_v2.typical_25 at 420112:421670 |
||||||||||||||||||
Issue descriptionDue to a loss in perf coverage due to a field trial configuration issue, bisect cannot identify the regressing changelist.
,
Oct 18 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8998424324615354016
,
Oct 18 2016
,
Oct 19 2016
===== BISECT JOB RESULTS ===== Status: failed ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@419896 505.85 28.1518 5 good chromium@421741 624.162 25.2639 5 bad Bisect job ran on: linux_perf_bisect Bug ID: 657187 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests page_cycler_v2.typical_25 Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-warm/http___www.theonion.com Relative Change: 23.39% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6781 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8998424324615354016 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5220399430762496 | 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 18 2016
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982651712527728480
,
Apr 12 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Please try rerunning the bisect. If failures persist contact the team (see below) and report the error. Bisect Details Configuration: linux_perf_bisect Benchmark : page_cycler_v2.typical_25 Metric : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___www.theonion.com Revision Result N chromium@419896 501.34 +- 138.238 14 good chromium@421741 619.267 +- 92.4592 14 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests page_cycler_v2.typical_25 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982651712527728480 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5220399430762496 | 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!
,
Apr 25 2017
,
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 robliao@chromium.org
, Oct 18 2016