New issue
Advanced search Search tips

Issue 762798 link

Starred by 1 user
Status: Assigned
Owner:
tikuta@chromium.org
Cc:
dpranke@chromium.org
ukai@chromium.org
tikuta@chromium.org
yyanagisawa@chromium.org
shinyak@chromium.org
sque@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Refactoring chromium recipe module to filter out the goma related code to goma module

Project Member Reported by tikuta@chromium.org, Sep 7 2017 
It is better to move goma related code to goma module and stop to enable goma in some recipe tests that are not for testing goma behavior.

This issue is derived from
https://chromium-review.googlesource.com/c/chromium/tools/build/+/654497#message-bc440a19da40c606a300c683f86a7cc13a1ee94c

Comment 1 by benhenry@google.com, Jan 10 

This bug had an unsupported status. Updating to Untriaged so someone will reevaluate.

Comment 2 by benhenry@google.com, Jan 10

Status: Untriaged

Comment 3 by benhenry@google.com, Jan 11

Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.
►

Sign in to add a comment