Thanks for reporting this issue, Allen. 

Could you give a little bit more context as to who the right owner(s) of the of a Chrome OS Test component would be? This will help us contact them and make sure they are aware of this issue. 

There is already a "Test" component, so it would seem reasonable to create Test > ChromeOS once we have the right POCs. 

jclinton, do you have any ideas?  This component should be valuable for the test health planning work.  Adding shaprioc too (although he's out at the moment).

One potential problem with creating "OS>Test" as a new component is that there is no dedicated Platform testing team. We would throw bugs there and they would likely never be triaged.

Instead, we should probably route failing tests to the right component under OS with a special label. If we are having trouble figuring out which team owns a failing test, that's something that Platform TPM's could help route. (Added Bernie to chime in on that part.)

+dchan

I think Danny's team might be considered a dedicated platform testing team, so if there are issues with the tests themselves they probably fall under his team's jurisdiction. 

If these are platform failures, then they should go to the appropriate component for triage by the individual platform area teams. 

Pinging this thread because the issues is still open and there has been no update in the last 2 weeks. Jason, Bernie and all, has there been any resolution here?

+efoo, since you have been spearheading some of the discussions around CrOS components. Is there any place you think this should live?

This is something I think Danny should decide. If one does not already exist, Danny's team should define a triage component or label for Chrome OS tests and work with triage for Infra>Client>ChromeOS>Test to define a triage rule. 

The description for Infra>Client>ChromeOS>Test should also be updated to state, **Do not use this component for test issues, file a bug under <label/component> instead**

My 2 cents. 

There is Infra>ChromeOS>Test and no Infra>Client>ChromeOS>Test? 
Is that one the same you refer to?

I see 189 bug without owner https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3DInfra%3EChromeOS%3ETest++-has%3Aowner&sort=-owner&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids

cindyb@ for resolution.

+cindyb, is that the right component? Also are we talking about only untriage and unconfirmed one?  https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3DInfra%3EChromeOS%3ETest++-has%3Aowner+status%3Auntriaged%2Cunconfirmed+&sort=-modified+-owner&colspec=ID+Pri+M+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids

The bug are file against infra, should the triage be handle by the infra team?

So there is a separation here we have:

1. Bugs related to the testing infrastructure.
2. Bugs related to tests.

My impression is that Infra...Test is 1, and should be triaged by someone on akeshet@'s team.

For 2, I think these go in the component for the area of Chrome OS for which they are relevant, e.g. a network test failure goes to the network component.

If we look at a few members of dchan@'s team their bugs are spread out quite a bit, which makes some sense, tests are generally related to some particular area of the overall product, the tests do not exist in isolation. https://bugs.chromium.org/p/chromium/issues/list?can=2&q=owner%3Aharpreet%40chromium.org%2Cdhaddock%40chromium.org%2Ckalin%40chromium.org%2Crohitbm%40chromium.org%2Cvsuley%40chromium.org%2Ckathrelkeld%40chromium.org%2Ckmshelton%40chromium.org&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids 

We do have a Test component, and we can take a look and see a wide spread of issues with owners beyond dchan@'s team (and even Chrome OS) so I don't think this is really usable a queue for the Chrome OS test team (though maybe this component with OS=Chrome?). https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3ATest+&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids

So I guess this boils down to, if one has a request for the test team, where would one file it so it gets to the right person? Which I think is a question for Danny, where would you to pick up bugs from? 

Do we need a Tests>ChromeOS or is Tests;OS=Chrome usable? Maybe something entirely different?