Building ash_unittests builds v8 |
||||
Issue descriptionGiven 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
,
Aug 24
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.
,
Aug 24
,
Aug 31
Afakhry@ who could we assign this to?
,
Sep 1
Not sure, let's keep up for grabs. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ovanieva@chromium.org
, Aug 24