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

Issue 594828 link

Starred by 1 user
Status: WontFix
Owner:
█ jrbarnette@chromium.org
Last visit > 30 days ago
Closed: Dec 2016
Cc:
█ shuqianz@chromium.org
xixuan@chromium.org
ayatane@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature
OKR



Sign in to add a comment

write to status.log from special tasks

Reported by jrbarnette@chromium.org, Mar 14 2016 
When provision fails, currently the only recourse to understand
the failure is to read the debug logs.  Reading the debug logs is
hell.  Instead, like Repair and Verify tasks, Provision tasks should
log basic information about actions and outcomes in status.log.

Comment 1 by akes...@chromium.org, Mar 28 2016

Cc: shuqianz@chromium.org
Labels: okr
If I understood our discussion correctly, we want to make Provision follow a similar (or the same) code path as the Verifiers.

This sounds like an okr candidate as part of our continuoud Provision clarification work.

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

Components: Infra>Client>ChromeOS
Labels: -Infra-ChromeOS

Comment 3 by autumn@chromium.org, Jun 27 2016

Owner: xixuan@chromium.org

Comment 4 by akes...@chromium.org, Sep 27 2016

Cc: ayatane@chromium.org
Labels: -okr OKR
What is the concrete request here? To log information in status.log from special tasks? Do we not already do that? If not, what does it win us?

Comment 5 by akes...@chromium.org, Sep 27 2016

Summary: write to status.log from special tasks (was: Make provision failure logs easier to diagnose)

Comment 6 by akes...@chromium.org, Dec 6 2016

Cc: xixuan@chromium.org
Owner: jrbarnette@chromium.org
Is this still relevant?

Comment 7 by jrbarnette@chromium.org, Dec 6 2016

Status: WontFix (was: Available)
> Is this still relevant?

In theory, yes.  In practice, I don't think there's a clear
and compelling case in _this_ bug for a specifically articulated
code change...
►

Sign in to add a comment