Issue metadata
Sign in to add a comment
|
11.5%-26.4% regression in media.android.tough_video_cases_tbmv2 at 473831:473887 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 30 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978200304750424512
,
May 30 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.common_mobile Metric : timeToFirstMeaningfulPaint_avg/browse_media/browse_media_facebook_photos 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=browse.media.facebook.photos system_health.common_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978200304750424512 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5274624922746880 | 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!
,
May 30 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978197202012563520
,
May 30 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.common_mobile Metric : timeToFirstMeaningfulPaint_avg/browse_media/browse_media_facebook_photos 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=browse.media.facebook.photos system_health.common_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978197202012563520 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5274624922746880 | 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!
,
May 30 2017
Set Speed>Bisection label because of the "Bisect failed for unknown reasons".
,
Jun 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976996827201587808
,
Jun 12 2017
Some of these are false alerts where the ref moved at the same time. A couple looked suspicious so I kicked off a bisect to find out what the culprit was. I they have recovered since so we can probably close this anyway.
,
Jun 12 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.common_mobile Metric : timeToFirstMeaningfulPaint_avg/browse_media/browse_media_facebook_photos Revision Result N chromium@473800 511.92 +- 190.749 21 good chromium@473900 529.306 +- 199.601 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=browse.media.facebook.photos system_health.common_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976996827201587808 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5249830512754688 | 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 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976974143320595504
,
Jun 13 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: INFRA_FAILURE The bisect was able to narrow the range, you can try running with: good_revision: 353a96e9ef4fe92c8808aac4acec49b2a7527109 bad_revision : 0e2a2278827bd1ef68423438211030a22b60e331 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.common_mobile Metric : timeToFirstMeaningfulPaint_avg/browse_media/browse_media_facebook_photos Revision Result N chromium@473800 430.67 +- 14.042 9 good chromium@473850 429.993 +- 15.3587 14 good chromium@473863 423.57 +- 16.9085 6 good chromium@473869 427.54 +- 13.7929 6 good chromium@473872 427.553 +- 17.6892 6 good chromium@473874 440.172 +- 8.48714 6 bad chromium@473875 443.414 +- 13.0913 6 bad chromium@473900 441.736 +- 34.9535 9 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=browse.media.facebook.photos system_health.common_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976974143320595504 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5249830512754688 | 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 17 2017
Some of these, the ref build is moving too, and they're invalid. For the regression in #11, it recovered a few revisions later. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by toyoshim@chromium.org
, May 30 2017