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

Issue 605721 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocked on:
issue 571088



Sign in to add a comment

last bit of dependent work for zergling support

Project Member Reported by kevcheng@chromium.org, Apr 21 2016

Issue description

This bug is just to cover the cbuildbot work needed for zergling support in the lab and depend on the auto-labeling bug (almost done!).  

https://docs.google.com/document/d/1O5o7rCnkaM_sA99_kyp1fonkuKbWlOYOQtgKMhgVq1w/edit?ts=5702d564

The cbuildbot changes needed is just to update the config to specify in the hwtest config the zergling boards.  Probably best to create a hwtest config that all the zergling boards can include.
 

Comment 1 by benhenry@google.com, Apr 26 2016

Components: Infra>Client>ChromeOS
Labels: -Infra-ChromeOS
Status: Started (was: Assigned)
I believe the only zergling boards are gnawty/gnawty+ and terra/terra13, will update the config for those two boards.
There is also kip and kip13 FWIW.
just an update:

I haven't yet started but plan to get to this next week.  There will be some changes necessary on the run_suite.py side of things as well but I think I have a general idea of how to go about things.  I'll want to bounce my ideas off Dan first before implementing though.  The changes do seem pretty straightforward so assuming my approach is good, I think this should be done by end of next week (cl out, not necessarily pushed to prod).
Status: Archived (was: Started)
Bulk closing Infra>Client>ChromeOS issues untouched in over a year.

Sign in to add a comment