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

Issue 699283 link

Starred by 1 user
Status: Archived
Owner:
█ bpeake@chromium.org
Last visit > 30 days ago
Closed: May 2018
Cc:
█ dshi@chromium.org
akes...@chromium.org
█ krisr@chromium.org
pprabhu@chromium.org
█ kevcheng@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Unittests for Testbeds

Project Member Reported by sbasi@chromium.org, Mar 7 2017 
We have no CQ coverage at all for testbeds, therefore breakages are not caught till test_push (or worst once they hit prod).

The easiest way to get some CQ coverage is to add unittests to the testbed class (and hopefully some to adb_host as well).

I spoke with Benny and he is willing to pick this up, thanks Benny.

Comment 1 by sbasi@chromium.org, Mar 7 2017

Cc: dshi@chromium.org kevcheng@chromium.org

Comment 2 by pprabhu@chromium.org, Mar 7 2017 

Thanks!

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

Labels: akeshet-pending-downgrade
ChromeOS Infra P1 Bugscrub.

P1 Bugs in this component should be important enough to get weekly status updates.

Is this already fixed?  -> Fixed
Is this no longer relevant? -> Archived or WontFix
Is this not a P1, based on go/chromeos-infra-bug-slo rubric? -> lower priority.
Is this a Feature Request rather than a bug? Type -> Feature
Is this missing important information or scope needed to decide how to proceed? -> Ask question on bug, possibly reassign.
Does this bug have the wrong owner? -> reassign.

Bugs that remain in this state next week will be downgraded to P2.

Comment 4 by akes...@chromium.org, Jul 24 2017

Labels: -akeshet-pending-downgrade Pri-2
ChromeOS Infra P1 Bugscrub.

Issue untouched in a week after previous message. Downgrading to P2.

Comment 5 by ayatane@chromium.org, May 15 2018

Status: Archived (was: Untriaged)
►

Sign in to add a comment