False rejects caused by telemetry unit_tests hitting timeout threshold |
|||
Issue descriptionExample build:https://ci.chromium.org/p/chromium/builders/luci.chromium.try/chromeos-amd64-generic-rel/160895 Note that in 'without_patch', shard #2 passes in 1191 seconds [1200 second timeout]. In 'with_patch' and 'retry_with_patch', shard#2 times out after 1200 seconds [most tests ran and passed]
,
Jan 4
I'm going to double the telemetry unit_tests timeout, given that the other shards are also within a factor of 2X of the timeout.
,
Jan 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/f521c8c4c26d86aec60a2e1497d31c36f042d155 commit f521c8c4c26d86aec60a2e1497d31c36f042d155 Author: erikchen <erikchen@chromium.org> Date: Fri Jan 04 20:03:09 2019 Double the timeout for telemetry_unittests on CrOS. Shards regularly take ~900s to run, and some shards are sitting very close to the 1200s threshold. This CL doubles the timeout to 2400s. Bug: 919113 Change-Id: I96597a6a33a7fb2143393ae9940956923f96fe79 Reviewed-on: https://chromium-review.googlesource.com/c/1396234 Reviewed-by: Stephen Martinis <martiniss@chromium.org> Commit-Queue: Erik Chen <erikchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#620040} [modify] https://crrev.com/f521c8c4c26d86aec60a2e1497d31c36f042d155/testing/buildbot/chromium.chromiumos.json [modify] https://crrev.com/f521c8c4c26d86aec60a2e1497d31c36f042d155/testing/buildbot/test_suites.pyl
,
Jan 10
,
Jan 11
|
|||
►
Sign in to add a comment |
|||
Comment 1 by erikc...@chromium.org
, Jan 4129 KB
129 KB View Download