Issue metadata
Sign in to add a comment
|
v8.infinite_scroll-classic_tbmv2 failing on 11 builders |
||||||||||||||||||||
Issue descriptionv8.infinite_scroll-classic_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 10.12 Perf: https://build.chromium.org/p/chromium.perf/builders/Mac%2010.12%20Perf - Mac Air 10.11 Perf: https://build.chromium.org/p/chromium.perf/builders/Mac%20Air%2010.11%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 ATI GPU Perf: https://build.chromium.org/p/chromium.perf/builders/Win%207%20ATI%20GPU%20Perf - Win 7 Intel GPU Perf: https://build.chromium.org/p/chromium.perf/builders/Win%207%20Intel%20GPU%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 The swarming page seems to indicate this is taking too long and timing out.
,
Jun 2 2017
this seems to have jumped from 13 m -> an hour or so
,
Jun 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: ab0c11df9302ab76649b00bd8ceba4dd7f886a11 bad_revision : 30ff36523161aea9df5d4e787aac0bb9d532a205 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: win_8_perf_bisect Benchmark : v8.infinite_scroll-classic_tbmv2 Metric : benchmark_duration/benchmark_duration Revision Result N chromium@475576 13.1724 +- 0.623381 6 good chromium@475663 34.5749 +- 27.5444 6 bad chromium@475749 34.5772 +- 12.3274 6 bad chromium@475921 31.2199 +- 18.5306 6 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-classic_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977879527403589312 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6228604939141120 | 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 3 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977819716084910560
,
Jun 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: ab0c11df9302ab76649b00bd8ceba4dd7f886a11 bad_revision : 30ff36523161aea9df5d4e787aac0bb9d532a205 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: win_8_perf_bisect Benchmark : v8.infinite_scroll-classic_tbmv2 Metric : benchmark_duration/benchmark_duration Revision Result N chromium@475576 12.9694 +- 0.56081 6 good chromium@475663 47.89 +- 31.4821 6 bad chromium@475749 32.6005 +- 12.5775 6 bad chromium@475921 29.1441 +- 6.75875 6 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-classic_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977819716084910560 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6228604939141120 | 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 4 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 10
Archiving issues with no priority, no component and no owner |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jun 2 2017