New issue
Advanced search Search tips

Issue 872371 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Task



Sign in to add a comment

Building ash_unittests builds v8

Project Member Reported by jamescook@chromium.org, Aug 8

Issue description

Given that we go to some trouble not to have content dependencies in ash_unittests, this seems unfortunate. (We have a separate ash_content_unittests for that.)

I wonder if there's an easy way around this.

jamescook@jamescook:/w/chrome/src (pointerwatcher)$ gn path out/Default //ash:ash_unittests //v8 --all

//ash:ash_unittests --[private]-->
//chromeos:test_support --[private]-->
//net:test_support --[public]-->
//net:net_with_v8 --[private]-->
//v8:v8

//ash:ash_unittests --[private]-->
//chromeos:test_support --[private]-->
//net:test_support --[public]-->
//net:net_with_v8 --[private]-->
//gin:gin --[public]-->
//v8:v8

 
jamescook@ which component can we assign here so that it doesn't show up in UI triage
Well, it's a general UI code problem, so UI>Shell is the right component.

I dunno what your triage filters look like, but you could mark Available.
Labels: Hotlist-CodeHealth
Components: -UI>Shell
Owner: afakhry@chromium.org
Status: Available (was: Untriaged)
Afakhry@ who could we assign this to?
Cc: afakhry@chromium.org
Components: Tests
Labels: -Type-Bug Type-Task
Owner: ----
Status: Untriaged (was: Available)
Not sure, let's keep up for grabs.

Sign in to add a comment