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

Issue 690164 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

[autotest] test push should verify the autotest code is on the same hash for all lab servers

Project Member Reported by dshi@chromium.org, Feb 8 2017

Issue description

The test push ran into an odd issue today. For some reason, drone and master scheduler stays on prod branch after deploy_server.py, but the shard is able to move to ToT.

We should have some verification in test_push script to make sure all test servers are on the same hash. Some simple ssh and git call should be able to achieve that.
 

Comment 1 by aut...@google.com, Feb 15 2017

Labels: -current-issue OS-iOS
Owner: shuqianz@chromium.org
Labels: -OS-iOS
will do
Status: Started (was: Untriaged)
Project Member

Comment 5 by bugdroid1@chromium.org, Jun 27 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/chromeos-admin/+/e19d15a93aed79d5c25b89f3b4b09e88ca5fbd06

commit e19d15a93aed79d5c25b89f3b4b09e88ca5fbd06
Author: Shuqian Zhao <shuqianz@chromium.org>
Date: Tue Jun 27 15:45:09 2017

Status: Fixed (was: Started)

Comment 7 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Sign in to add a comment