Issue metadata
Sign in to add a comment
|
66.3%-205.3% regression in system_health.common_mobile at 450189:450239 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 16 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8987514793695647872
,
Feb 16 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_one_perf_bisect Benchmark : system_health.common_mobile Metric : timeToFirstContentfulPaint_avg/load_media/load_media_flickr Revision Result N chromium@450188 2912.83 +- 1136.12 21 good chromium@450239 2831.25 +- 1248.95 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.media.flickr system_health.common_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8987514793695647872 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6453858026389504 | 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!
,
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 alexclarke@chromium.org
, Feb 16 2017