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

Issue 801909 link

Starred by 1 user
Status: Fixed
Owner:
█ benhenry@chromium.org
Last visit > 30 days ago
Closed: Jan 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: ----
Type: ----



Sign in to add a comment

[Component Request] Tests>Tast

Project Member Reported by derat@chromium.org, Jan 14 2018 
1] Component Name: Tast

2] Parent Component (e.g. Blink, UI>Browser, etc...): Tests

3] Description of Component: Tast (Chrome OS integration testing system, go/tast)

4] Admin/ Owner: derat@chromium.org

5] Please specify what triage practices will be followed for the component
(i.e. what team will do it and how frequently).

I will triage bugs continuously as they are filed.

Thanks!

Comment 1 by derat@chromium.org, Jan 19 2018

Cc: aga...@chromium.org
Are these requests typically handled by the trooper, or is there another rotation for label/component creation? (Or are the instructions that pointed me here outdated?)

Comment 2 by aga...@chromium.org, Jan 19 2018

Cc: -aga...@chromium.org
These requests are never handled by the trooper; they're handled by the TPMs who manage our monorail project configuration (i.e. kerz and others). I don't know what their triage process / SLO for this component is.

Comment 3 by derat@chromium.org, Jan 19 2018

Owner: kerz@chromium.org
Jason, can you add this component to monorail (or suggest someone to do that)? Thanks!

Comment 4 by k...@google.com, Jan 23 2018

Owner: benhenry@chromium.org
Adding Ben who I think can take a look.

Comment 5 by benhenry@google.com, Jan 23 2018

Status: Fixed (was: Untriaged)
Created.
►

Sign in to add a comment