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

Issue 920053 link

Starred by 1 user

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Get developer wifi cells up and running in B1600

Project Member Reported by harpreet@chromium.org, Jan 9

Issue description

These are to be used by WiFi developers during device bring up phase to
allow for scheduled suites to run on these devices.


Things to do:
1. update DHCP; allocate hostnames / IPs for devs
2. potentially create a separate test suite / pool of devices for devs? not sure if this is needed; to be discussed
3. write a short doc listing the steps dev's need to complete to get tests up and running on newly installed devices in dev cells
 
A port in second floor lab was patched to cros_sys_high_touch lab network on the first floor since this lab already has the needed devservers to schedule / run autotests.

https://gutsv3.corp.google.com/#ticket/36826347
Project Member

Comment 2 by bugdroid1@chromium.org, Jan 9

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

commit 7a6812a467e90a31d88031893926cf051fdd542a
Author: harpreet <harpreet@google.com>
Date: Wed Jan 09 21:58:50 2019

Sign in to add a comment