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

Issue 697710 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocking:
issue 694730



Sign in to add a comment

ReportStageFailureToCIDB for nested CompoundFailure

Project Member Reported by nxia@chromium.org, Mar 2 2017

Issue description

CompoundFailure may be nested, ReportStageFailureToCIDB should insert all exceptions into failureTable.

+---------+----------------+------------------+----------------+---------------------------------------------------------------------+--------------------+------------+---------------------+
| id      | build_stage_id | outer_failure_id | exception_type | exception_message                                                   | exception_category | extra_info | timestamp           |
+---------+----------------+------------------+----------------+---------------------------------------------------------------------+--------------------+------------+---------------------+
| 1895129 |       38053984 |          1895127 | TestLabFailure | ** HWTest did not complete due to infrastructure issues (code 3) ** | lab                | NULL   
 

Comment 1 by nxia@chromium.org, Mar 2 2017

Looks like CreateExceptInfo has flattened CompoundFailure. Reporting exc_infos for CompoundFailure should be enough for now.

https://cs.corp.google.com/chromeos_public/chromite/lib/failures_lib.py?type=cs&q=CreateExceptInfo&sq=package:%5Echromeos_(internal%7Cpublic)$&l=68

Comment 2 by nxia@chromium.org, Apr 5 2017

Status: WontFix (was: Untriaged)

Sign in to add a comment