New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 796275 link

Starred by 1 user
Status: Duplicate
Merged: issue 808563
Owner:
akes...@chromium.org
Closed: Feb 2018
Cc:
█ jrbarnette@chromium.org
█ martinroth@chromium.org
shapiroc@chromium.org
█ bmgordon@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: ----



Sign in to add a comment

bvt-arc times out across boards

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Dec 19 2017 
Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of bmgordon@google.com

The bvt-arc suite is timing out on quite a few boards.  General symptoms:

* There is a 15-60 minute gap between scheduling the tests and the first test starting.
* Once the tests start, they seem to run normally.  None fail.
* The suite is aborted after a timeout.  How far it gets before the timeout seems to be correlated with the length of the scheduling delay.

Examples:
- cave-release:  https://luci-milo.appspot.com/buildbot/chromeos/cave-release/1775
- celes-release: https://luci-milo.appspot.com/buildbot/chromeos/celes-release/1772
- lulu-release: https://luci-milo.appspot.com/buildbot/chromeos/lulu-release/1776
- poppy-release: https://luci-milo.appspot.com/buildbot/chromeos/poppy-release/1029
- relm-release: https://luci-milo.appspot.com/buildbot/chromeos/relm-release/1775
- sentry-release: https://luci-milo.appspot.com/buildbot/chromeos/sentry-release/1773
- ultima-release: https://luci-milo.appspot.com/buildbot/chromeos/ultima-release/1777

Comment 1 by bmgordon@chromium.org, Dec 19 2017

Cc: martinroth@chromium.org jrbarnette@chromium.org
Components: Infra>Client>ChromeOS

Comment 2 by bmgordon@chromium.org, Dec 20 2017 

Another one today:

https://luci-milo.appspot.com/buildbot/chromeos/ultima-release/1780

Timeline:

4:46: 38 tests scheduled
5:15: First test starts running
6:21: 34th test finishes successfully
7:48: Suite is aborted because it times out.

There are no log messages between 6:26 and 7:48.  This sounds at least superficially similar to  crbug.com/796439 .

Comment 3 by bmgordon@chromium.org, Dec 22 2017 

A bunch more today:

https://luci-milo.appspot.com/buildbot/chromeos/caroline-release/1325
https://luci-milo.appspot.com/buildbot/chromeos/cave-release/1785
https://luci-milo.appspot.com/buildbot/chromeos/relm-release/1785
https://luci-milo.appspot.com/buildbot/chromeos/setzer-release/1778
https://luci-milo.appspot.com/buildbot/chromeos/squawks-release/2067
https://luci-milo.appspot.com/buildbot/chromeos/terra-release/1787
https://luci-milo.appspot.com/buildbot/chromeos/wizpig-release/1791

There may be two separate bugs here, because the delay happens in two places:

1. A long delay between scheduling all the suites and starting the first test.  These usually run until the timeout once they start.

2. Some of the tests run fairly soon after scheduling, and then there's a long delay with no output before the timeout.

Comment 4 by semenzato@chromium.org, Dec 29 2017

Labels: OS-Chrome
Mergedinto: 797849
Status: Duplicate (was: Available)
By mistake we started working on this on  issue 797849 .

Comment 7 by akes...@chromium.org, Jan 26 2018 

Numerous tko issues plagued us today. Let's hold open and revisit tomorrow.

Comment 8 by bmgordon@chromium.org, Feb 2 2018

Mergedinto: -797849 808563
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment