Who is triaging the Blink>Infra component?

20 views
Skip to first unread message

Philip Jägenstedt

unread,
Oct 5, 2017, 1:22:23 PM10/5/17
to blink-infra, Robert Ma
Context: https://bugs.chromium.org/p/chromium/issues/detail?id=770028

There are some things in the Blink>Infra component that might be relevant to ecosystem infra. Is there a rotation for doing bug triage there?

Dirk Pranke

unread,
Oct 5, 2017, 3:11:23 PM10/5/17
to Philip Jägenstedt, blink-infra, Robert Ma
I believe qyearsley@ and jeffcarp@ were looking at it fairly regularly, but no longer are, so there is no current rotation.

-- Dirk

On Thu, Oct 5, 2017 at 10:22 AM, Philip Jägenstedt <foo...@chromium.org> wrote:
Context: https://bugs.chromium.org/p/chromium/issues/detail?id=770028

There are some things in the Blink>Infra component that might be relevant to ecosystem infra. Is there a rotation for doing bug triage there?

--
You received this message because you are subscribed to the Google Groups "blink-infra" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-infra+unsubscribe@chromium.org.
To post to this group, send email to blink...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-infra/CAARdPYdLZy%2BQdHAzjFaesyM9eTDJD5S_X6qnWwi%3DpgU%2Biia8MA%40mail.gmail.com.

Dirk Pranke

unread,
Oct 5, 2017, 3:12:51 PM10/5/17
to Philip Jägenstedt, blink-infra, Robert Ma
That specific bug I'd expect someone on the CC team to handle, though; historically blink infra folks haven't spent too much time actually determining which things are tested and how unless they were also active blink devs (like I was).

-- Dirk

Quinten Yearsley

unread,
Oct 5, 2017, 10:43:11 PM10/5/17
to Dirk Pranke, Philip Jägenstedt, blink-infra, Robert Ma
On Thu, Oct 5, 2017 at 12:11 PM, Dirk Pranke <dpr...@chromium.org> wrote:

I believe qyearsley@ and jeffcarp@ were looking at it fairly regularly, but no longer are, so there is no current rotation.

-- Dirk


This is accurate.

I intended to continue triaging Blink>Infra (for at least the rest of 2017), but haven't had any specific goals with regard to response time etc. and in practice haven't been triaging regularly in the past month.

Philip Jägenstedt

unread,
Oct 17, 2017, 6:02:25 AM10/17/17
to Quinten Yearsley, Dirk Pranke, blink-infra, Robert Ma, ecosystem-infra

Hmm, the lack of regular triage sounds like a problem. Since we've already agreed that some of what the blink infra team has done will make sense for ecosystem infra team, especially around LayoutTests, I've added experimental Blink>Infra triage section to the ecosystem infra rotation:

Everyone who's on rotation, please share you experience about what you find when triaging Blink>Infra. Maybe we'll need more components, or remove some components, before everything will make sense.

Jonathon Kereliuk

unread,
Oct 17, 2017, 12:21:20 PM10/17/17
to Philip Jägenstedt, Quinten Yearsley, Dirk Pranke, blink-infra, Robert Ma, ecosystem-infra
From the times I have done triaging on Blink>Infra during rotation, there has not been many bugs; however, looking there now shows a lot of them.
The bugs I have seen I usually found I lack the context on the specific area (usually exporter or something), and try to find someone (usually Robert), who has more context and can take a look.

I'm not sure how granular labels are usually for bug tracking, but maybe we could have separate labels for things that are more specifically WPT or Layout Tests or exporter/importer?

--
You received this message because you are subscribed to the Google Groups "ecosystem-infra" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ecosystem-infra+unsubscribe@chromium.org.
To post to this group, send email to ecosyst...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/ecosystem-infra/CAARdPYehN9%2BGxRcqsjYK0jWuTZk7tnOmiCWfbZL6X3yMu8crXg%40mail.gmail.com.

Quinten Yearsley

unread,
Oct 17, 2017, 12:49:45 PM10/17/17
to Jonathon Kereliuk, Philip Jägenstedt, Dirk Pranke, blink-infra, Robert Ma, ecosystem-infra
Currently, for issues related to WPT or importer/exporter the component is Blink>Infra>Ecosystem, and for layout tests in general, it's Blink>Infra. There's also Blink>Infra>Predictability, which so far has mainly been used for work related to use counters.

Philip Jägenstedt

unread,
Oct 17, 2017, 2:23:46 PM10/17/17
to Quinten Yearsley, Jonathon Kereliuk, cha...@chromium.org, Dirk Pranke, blink-infra, Robert Ma, ecosystem-infra
Blink>Infra>Predictability should be unused by now, but I see there are two issues there. It doesn't show up in autocomplete. +Jason Chase, did you take care of that? What should we do with the remaining two issues?

On Tue, Oct 17, 2017 at 6:49 PM Quinten Yearsley <qyea...@google.com> wrote:
Currently, for issues related to WPT or importer/exporter the component is Blink>Infra>Ecosystem, and for layout tests in general, it's Blink>Infra. There's also Blink>Infra>Predictability, which so far has mainly been used for work related to use counters.
On Tue, Oct 17, 2017 at 9:21 AM, Jonathon Kereliuk <kere...@chromium.org> wrote:
From the times I have done triaging on Blink>Infra during rotation, there has not been many bugs; however, looking there now shows a lot of them.
The bugs I have seen I usually found I lack the context on the specific area (usually exporter or something), and try to find someone (usually Robert), who has more context and can take a look.

I'm not sure how granular labels are usually for bug tracking, but maybe we could have separate labels for things that are more specifically WPT or Layout Tests or exporter/importer?
On Tue, Oct 17, 2017 at 6:02 AM, Philip Jägenstedt <foo...@chromium.org> wrote:

Hmm, the lack of regular triage sounds like a problem. Since we've already agreed that some of what the blink infra team has done will make sense for ecosystem infra team, especially around LayoutTests, I've added experimental Blink>Infra triage section to the ecosystem infra rotation:

Everyone who's on rotation, please share you experience about what you find when triaging Blink>Infra. Maybe we'll need more components, or remove some components, before everything will make sense.

On Fri, Oct 6, 2017, 04:43 Quinten Yearsley <qyea...@google.com> wrote:
On Thu, Oct 5, 2017 at 12:11 PM, Dirk Pranke <dpr...@chromium.org> wrote:

I believe qyearsley@ and jeffcarp@ were looking at it fairly regularly, but no longer are, so there is no current rotation.

-- Dirk


This is accurate.

I intended to continue triaging Blink>Infra (for at least the rest of 2017), but haven't had any specific goals with regard to response time etc. and in practice haven't been triaging regularly in the past month.

--
You received this message because you are subscribed to the Google Groups "ecosystem-infra" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ecosystem-inf...@chromium.org.

Jason Chase

unread,
Oct 17, 2017, 3:29:46 PM10/17/17
to Philip Jägenstedt, Quinten Yearsley, Jonathon Kereliuk, cha...@chromium.org, Dirk Pranke, blink-infra, Robert Ma, ecosystem-infra
Yes, I deprecated the Blink>Infra>Predictability component, so it doesn't show up in auto-complete.

Rick, Philip and I had a brief conversation about the deprecation back in September. I left the two issues in the component because there wasn't a better component (we don't have an umbrella Predictability component). One of the bugs (646686) is assigned and marked with another component, so I'd suggest it's fine as is. The other (729137) could potentially fall through the cracks, so I'd suggest Rick (the reporter) move it as desired.

Thanks,
Jason

To unsubscribe from this group and stop receiving emails from it, send an email to ecosystem-infra+unsubscribe@chromium.org.

Rick Byers

unread,
Oct 18, 2017, 8:40:50 PM10/18/17
to Jason Chase, Philip Jägenstedt, Quinten Yearsley, Jonathon Kereliuk, Dirk Pranke, blink-infra, Robert Ma, ecosystem-infra
Updated both bugs so Blink>Infra>Predictability is now empty.

Reply all
Reply to author
Forward
0 new messages