New issue
Advanced search Search tips

Issue 802035 link

Starred by 3 users
Status: Fixed
Owner:
jbudorick@chromium.org
Closed: Jan 2018
Cc:
w...@chromium.org
dpranke@chromium.org
jbudorick@chromium.org
chanli@chromium.org
seanmccullough@chromium.org
liaoyuke@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Android CQ overall build timeouts are inconsistently low

Project Member Reported by gab@chromium.org, Jan 15 2018 
In CQ, had an unrelated(?) failure on https://ci.chromium.org/buildbot/tryserver.chromium.android/android_n5x_swarming_rel/340283 where the stdout for the reported failing suite looks like

I  586.604s run_tests_on_device(004906f7965d4354)  [----------] Global test environment tear-down
I  586.604s run_tests_on_device(004906f7965d4354)  [==========] 256 tests from 41 test cases ran. (12323 ms total)
I  586.604s run_tests_on_device(004906f7965d4354)  [  PASSED  ] 256 tests.
I  586.604s run_tests_on_device(004906f7965d4354)  <<ScopedMainEntryLogger
I  586.613s run_tests_on_device(004906f7965d4354)  Finished running tests on this device.
I  586.643s Main  FINISHED TRY #2/3
I  586.643s Main  All tests completed.

(full @ https://logs.chromium.org/v/?s=chromium%2Fbb%2Ftryserver.chromium.android%2Fandroid_n5x_swarming_rel%2F340283%2F%2B%2Frecipes%2Fsteps%2Fnet_unittests__with_patch__on_Android%2F0%2Fstdout)

What's the issue? Why is this flaking?

Comment 1 by w...@chromium.org, Jan 16 2018

Cc: dpranke@chromium.org jbudorick@chromium.org
Labels: M-66
gab: The bot will regard the test as having failed, even though it actually succeeded, if it is unable to get the summary-results file from the swarming shard, IIRC.

Is that step more unreliable on Android/Fuchsia/other device using bots, perhaps?

Comment 2 by jbudorick@chromium.org, Jan 16 2018

Components: Infra>Client>Chrome
Owner: jbudorick@chromium.org
Status: Assigned (was: Untriaged)
That build's compile took 1h26m, so the build hit the overall 1h55m build timeout: https://codesearch.chromium.org/chromium/build/masters/master.tryserver.chromium.android/builders.pyl?rcl=1e8a734fb625509af85b2c4d58108a9fbb799bbd&l=142

The timeout is outdated at this point, though; the default in most other locations got bumped up to 4h a while ago.

I'll update the timeouts. martiniss@ is investigating compile resources in a more general sense over in https://bugs.chromium.org/p/chromium/issues/detail?id=799603.

Comment 3 by jbudorick@chromium.org, Jan 16 2018

Summary: Android CQ overall build timeouts are inconsistently low (was: Test suite fails despite passing all tests?)
Project Member

Comment 4 by bugdroid1@chromium.org, Jan 17 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/68b30f2efc06466fca3ab3f5bdd0ce65dce65cc0

commit 68b30f2efc06466fca3ab3f5bdd0ce65dce65cc0
Author: John Budorick <jbudorick@chromium.org>
Date: Wed Jan 17 00:06:23 2018

Update build timeouts for tryserver.chromium.android.

This raises all build timeouts on tryserver.chromium.android to a
minimum of 4 hours, matching the current value of
master_utils.CQ_MAX_TIME (https://goo.gl/3eavjC).

Bug:  802035 
Change-Id: I4b29dd5bf59819016d07420945a2a03906d29c72
Reviewed-on: https://chromium-review.googlesource.com/868843
Reviewed-by: Benjamin Pastene <bpastene@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>

[modify] https://crrev.com/68b30f2efc06466fca3ab3f5bdd0ce65dce65cc0/masters/master.tryserver.chromium.android/builders.pyl

Comment 5 by jbudorick@chromium.org, Jan 17 2018

Status: Started (was: Assigned)
Going to wait until either late tonight or tomorrow AM to restart tryserver.chromium.android to pick up #4.

Comment 6 by jbudorick@chromium.org, Jan 17 2018 

Issue 797441 has been merged into this issue.
Project Member

Comment 7 by bugdroid1@chromium.org, Jan 17 2018 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/master-manager/+/0110470ae40360ac3b8cb886520b180de54ba144

commit 0110470ae40360ac3b8cb886520b180de54ba144
Author: John Budorick <jbudorick@google.com>
Date: Wed Jan 17 16:49:43 2018

Comment 8 by jbudorick@chromium.org, Jan 17 2018

Status: Fixed (was: Started)
►

Sign in to add a comment