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

Issue 837458 link

Starred by 3 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

UI to Lock DUT and request Englab team support.

Project Member Reported by dgarr...@chromium.org, Apr 27 2018

Issue description

Increasingly, the deputy ends up identifying a problem with a DUT, locking it, and handing it over to the Englab team.

Since we are building a new UI for Skylab, we should have a UI for doing this easily, including filing the relevant bugs (and linking for updates/details).

 
Cc: pboggini@chromium.org englab-sys-cros@google.com
See also bug 825342 which requests a standardized way to indicate
when a DUT has been removed and is awaiting replacement hardware.
Devices handed over in this way need to be marked so that they can
be distinguished by inventory tools.

I should also note that simply handing problems over to englab-sys-cros@
isn't a solution by itself.  Before any DUT is handed over, some work needs
to be done by the engineering team to debug what is actually wrong, and
specific instructions on the action needed should be provided with any
handover.

Components: -Infra>Client>ChromeOS Infra>Client>ChromeOS>Test
Owner: ----
Status: Available (was: Untriaged)
Labels: -Type-Bug -Pri-3 Pri-2 Type-Feature
Labels: Hotlist-Skylab
There are other labs that englab-sys-cros does not support.  I would prefer a way to specify which group/owner gets contacted for a particular lab vs spamming englab-sys-cros@ as a default.

Sign in to add a comment