Issue metadata
Sign in to add a comment
|
v8.infinite_scroll_tbmv2 failing on 11 builders |
||||||||||||||||||||||
Issue descriptionv8.infinite_scroll_tbmv2 failing on 11 builders Builders failed on: - Mac 10.11 Perf: https://build.chromium.org/p/chromium.perf/builders/Mac%2010.11%20Perf - Mac Air 10.11 Perf: https://build.chromium.org/p/chromium.perf/builders/Mac%20Air%2010.11%20Perf - Mac Pro 10.11 Perf: https://build.chromium.org/p/chromium.perf/builders/Mac%20Pro%2010.11%20Perf - Mac Retina Perf: https://build.chromium.org/p/chromium.perf/builders/Mac%20Retina%20Perf - Win 10 High-DPI Perf: https://build.chromium.org/p/chromium.perf/builders/Win%2010%20High-DPI%20Perf - Win 10 Perf: https://build.chromium.org/p/chromium.perf/builders/Win%2010%20Perf - Win 7 Nvidia GPU Perf: https://build.chromium.org/p/chromium.perf/builders/Win%207%20Nvidia%20GPU%20Perf - Win 7 Perf: https://build.chromium.org/p/chromium.perf/builders/Win%207%20Perf - Win 7 x64 Perf: https://build.chromium.org/p/chromium.perf/builders/Win%207%20x64%20Perf - Win 8 Perf: https://build.chromium.org/p/chromium.perf/builders/Win%208%20Perf - Win Zenbook Perf: https://build.chromium.org/p/chromium.perf/builders/Win%20Zenbook%20Perf
,
Apr 29 2017
=== Auto-CCing suspected CL author pmarko@chromium.org === Hi pmarko@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Test failure found with culprit Suspected Commit Author : pmarko Commit : 93bc5d7c02d275d27c030ab15a8c68efc8efdd99 Date : Thu Apr 27 10:58:28 2017 Subject: Enable client certificate patterns in device ONC policy Bisect Details Configuration: mac_pro_perf_bisect Benchmark : v8.infinite_scroll_tbmv2 Metric : benchmark_duration/benchmark_duration Revision Exit Code N chromium@467625 0 +- N/A 1 good chromium@467630 0 +- N/A 1 good chromium@467632 0 +- N/A 1 good chromium@467633 0 +- N/A 1 good chromium@467634 1 +- N/A 1 bad <-- chromium@467642 1 +- N/A 1 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 --story-filter=flickr v8.infinite_scroll_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981023546730668288 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5861243191033856 | 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 2 2017
@ulan (as owner of the perf test): I think v8.infinite_scroll_tbmv2 is failing randomly on that builder[1] and my CL was just there when it started failing. It is not failing in the newest build. I don't think my CL can really be the culprit as it is Chrome OS-specific. Please correct me if I'm wrong or if I should follow additional steps to ensure this. [1] https://build.chromium.org/p/chromium.perf/builders/Mac%20Pro%2010.11%20Perf?numbuilds=100
,
May 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980710462163362176
,
May 2 2017
pmarko@, I think you're right. It looks like the failure is flaky and the bisect got confused. I kicked of another bisect: https://chromeperf.appspot.com/buildbucket_job_status/8980710462163362176
,
May 2 2017
I think this is a dupe of 717078 which is fixed.
,
May 3 2017
Thanks for clearing that up! BTW how did you find out about this bug ( bug 716641 )?
,
May 3 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: 07cbcdc2a6293bba57b711d5d449c91a0a0541bc bad_revision : c18764a33a595baab6ba35a1447e51c7c74b6e30 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: win_8_perf_bisect Benchmark : v8.infinite_scroll_tbmv2 Metric : benchmark_duration/benchmark_duration Revision Exit Code N chromium@467615 0 +- N/A 20 good chromium@467624 0 +- N/A 20 good chromium@467633 1 +- N/A 20 bad chromium@467650 1 +- N/A 20 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 v8.infinite_scroll_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980710462163362176 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6387704310267904 | 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 3 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980597993152619760
,
May 4 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: 07cbcdc2a6293bba57b711d5d449c91a0a0541bc bad_revision : c18764a33a595baab6ba35a1447e51c7c74b6e30 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: win_8_perf_bisect Benchmark : v8.infinite_scroll_tbmv2 Metric : benchmark_duration/benchmark_duration Revision Exit Code N chromium@467615 0 +- N/A 20 good chromium@467624 0 +- N/A 20 good chromium@467633 1 +- N/A 20 bad chromium@467650 1 +- N/A 20 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 v8.infinite_scroll_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980597993152619760 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6387704310267904 | 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! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Apr 29 2017