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

Issue 722591 link

Starred by 1 user
Status: Archived
Owner:
ayatane@chromium.org
Closed: Oct 25
Cc:
akes...@chromium.org
█ chingcodes@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Provision test failures not being reported well

Project Member Reported by davidri...@chromium.org, May 15 2017 
The following build failed in a manner that looks like the tests failed:
https://uberchromegw.corp.google.com/i/chromeos/builders/link-paladin/builds/28322

In reality, the provision failures are the source of the problems:
https://viceroy.corp.google.com/chromeos/suite_details?build_id=1519422

If you closely read the full logs, you can see the provision failures, and the fact that the suite timed out as the final cause of failure, but it would be better if it was more obvious.

Comment 1 by jrbarnette@chromium.org, May 18 2017

Owner: ayatane@chromium.org
Status: Assigned (was: Untriaged)
We're planning to separate out provisioning to a separately
logged operation, which should make this problem better, if
not completely fixed.  ayatane@ will be able to say more.

In any event, this particular problem is a few steps removed
from any improvements in my queue.

Comment 2 by ayatane@chromium.org, Oct 9 2017

Labels: -Pri-2 Pri-3

Comment 3 by cindyb@chromium.org, Jun 8 2018 

Hi, this bug has not been updated recently. Please acknowledge the bug and provide status within two weeks (6/22/2018), or the bug will be closed. Thank you.

Comment 4 by ayatane@chromium.org, Oct 25

Status: Archived (was: Assigned)
►

Sign in to add a comment