v8.infinite_scroll-turbo_tbmv2 failing on 3 builders |
|||
Issue descriptionv8.infinite_scroll-turbo_tbmv2 failing on 3 builders Type: build-failure Builders failed on: - Mac 10.12 Perf: https://build.chromium.org/p/chromium.perf/builders/Mac%2010.12%20Perf - Win 10 High-DPI Perf: https://build.chromium.org/p/chromium.perf/builders/Win%2010%20High-DPI%20Perf - Win Zenbook Perf: https://build.chromium.org/p/chromium.perf/builders/Win%20Zenbook%20Perf Two types of errors: 1. shard #0 timed out, took too much time to complete 2. shard #0 expired, not enough capacity Maybe related to issue 685240 .
,
Jan 25 2017
Several other tests on the bot also has the same problem.
,
Jan 26 2017
Which bot are you referring to?
,
Jan 26 2017
All 3 bots here have multiple tests failing for the shard #0 timed out or expired error.
,
Jan 26 2017
Also seen a lot of similar failures on Mac Mini 8GB 10.12 Perf: https://luci-milo.appspot.com/buildbot/chromium.perf/Mac%20Mini%208GB%2010.12%20Perf/
,
Feb 13 2017
,
Feb 13 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/549d1501a66ed2ec0283149f65c71d64569183aa commit 549d1501a66ed2ec0283149f65c71d64569183aa Author: martiniss <martiniss@chromium.org> Date: Mon Feb 13 23:56:46 2017 chromium.perf.json: Special case some desktop bots This should help alleviate capacity issues we've been having for a bit. Longer-term solutions should be coming for this, but these particular bots are a bit overloaded right now. PERF SHERIFFS: This CL will cause changes to the following benchmarks * page_cycler_v2.intl_hi_ru on Mac 10.12 Perf * blink_perf.parser on Mac 10.12 Perf It also affects two other benchmarks, but those are already not sending data, because of missing capacity, so those won't cause any jumps in timings. BUG= 687425 , 680360 , 685275 Review-Url: https://codereview.chromium.org/2692133002 Cr-Commit-Position: refs/heads/master@{#450159} [modify] https://crrev.com/549d1501a66ed2ec0283149f65c71d64569183aa/testing/buildbot/chromium.perf.json
,
Mar 24 2017
This is passing after increased timeouts. |
|||
►
Sign in to add a comment |
|||
Comment 1 by zh...@chromium.org
, Jan 25 2017