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

Issue 745055 link

Starred by 1 user
Status: Archived
Owner:
█ shuqianz@chromium.org
Last visit > 30 days ago
Closed: Apr 2018
Cc:
akes...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

add devserver health check before testing push

Project Member Reported by shuqianz@chromium.org, Jul 17 2017 
Dedicated devservers in testing push are flaky. Propose to add devserver health check before really kicking off tests on the DUTs, so that we can know the devserver flaky issue ASAP and thus won't waste time and resources running tests.

Comment 1 by akes...@chromium.org, Jul 17 2017 

Is this in relation to the testbed issue? I thought the problem there was that those devices aren't in our dedicated "test push lab" rack, and use different devservers.

Comment 2 by shuqianz@chromium.org, Jul 18 2017 

Yes, the android DUTs are in a different lab from the cros DUTs, but we also add a dedicated devserver in the android lab in order to add devserver testing. The failed devserver(100.107.126.137) in crbug.com/743077, whose hostname is android1758-infra-devserver5, is the dedicated one. So, test push has two labs, chromeos and android lab, each of them has dedicated devserver set up.

So, the issue is caused by the only one dedicated test push devserver in the android lab was down.

Comment 3 by shuqianz@chromium.org, Apr 30 2018

Status: Archived (was: Untriaged)
►

Sign in to add a comment