Issue metadata
Sign in to add a comment
|
23.4%-39.3% regression in loading.mobile at 456172:456232 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8985234948797738960
,
Mar 14 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : loading.mobile Metric : timeToFirstContentfulPaint_avg/Regular-3G/http___news.yahoo.com_were-top-10-most-visited-us-national-parks-105323727.html Revision Result N chromium@456171 9687.82 +- 6218.86 21 good chromium@456232 9275.17 +- 1439.83 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...news.yahoo.com.were.top.10.most.visited.us.national.parks.105323727.html loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8985234948797738960 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5887563291688960 | 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!
,
Jun 2 2017
this recovered. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by hjd@chromium.org
, Mar 13 2017