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

Issue 624133 link

Starred by 2 users

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature



Sign in to add a comment

Add information to metadata.json about which suites were kicked off

Project Member Reported by leecy@chromium.org, Jun 28 2016

Issue description

Some test suites have dependencies (e.g. if AU tests fail, some suites are not kicked off).  GoldenEye currently doesn't have any way to know that these are missing because it wasn't kicked off due to dependency vs. kicked off but missing for other reasons.  Aviv mentioned in the sync meeting today that this information could be output in the metadata.json so we could display this in the UI differently.
 

Comment 1 by autumn@chromium.org, Jun 28 2016

Labels: -current-issue
Owner: akes...@chromium.org
Owner: leecy@chromium.org
Status: Assigned (was: Untriaged)
Is this issue still relevant?

If so, should be simple to implement the above approach.
Status: Archived (was: Assigned)
Bulk closing Infra>Client>ChromeOS issues untouched in over a year.

Sign in to add a comment