--
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.
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/BLUPR0501MB8523FC3DA834E5C59765206DF960%40BLUPR0501MB852.namprd05.prod.outlook.com.
I get some of these notifications as well, and I always archive them without reading. That's because unless I were to process all of them carefully, there's little chance that the ones I look at are the most important test failures to investigate.What I'd find useful is an easy way to list all problems relating to LayoutTests/external/wpt/foo, combining TestExpectations, W3CImportExpectations and -expected.txt files. On top of that, maybe something like the Blink bug status mails with links to click through to details.At some point there may be parts of the test suite that are so green that reacting to each new failure makes sense, and then perhaps opting in to notifications like these would be useful.
On Tue, Sep 5, 2017 at 9:39 PM Domenic Denicola <d...@domenic.me> wrote:
+ricea@ and I help maintain the streams/ directory. I think we generally find them a bit spammy (but not horribly so). Some main reasons are:
* Mostly they just notify us of changes that we ourselves made upstream via GitHub. So this doesn't help us much.
* What I really care about is whether any of the imported tests are marked as failing. Figuring this out takes extra work to dig into the CL and find -expected.txt files or changes.
* Most of the emails are bots talking to themselves and approving each other. Generally you get 6 emails for any given import: 3 from "Blink WPT Bot (Gerrit)", 2 from "Commit Bot (Gerrit)", and then one from "Quinten Yearsley (Gerrit)". Only the first of those emails has useful content.
So indeed something like an email summarizing successful imports, especially if it highlighted newly-failing tests with easily clickable links to the -expected.txt files, would be better.
--
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/BLUPR0501MB8523FC3DA834E5C59765206DF960%40BLUPR0501MB852.namprd05.prod.outlook.com.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYf0nO-pQhVYPzPMyrquppaamzU-MFZP0jf%2B%3Du1o515UxA%40mail.gmail.com.
We get these notifications to our list, style-dev@. I don't think anyone on my team actually reads them, because a wide range of stuff goes to style-dev (often things we didn't work on), so it's mostly just noise to us.Some feedback summarised from a quick team discussion:- We don't send any other CLs to style-dev@, so it feels particularly spammy when robot CLs cc us- We don't understand why we're getting cc'd on these CLs- They don't require any action from us- We wouldn't know what to do if the import failedOn Wed, Sep 6, 2017 at 9:58 PM, 'Philip Jägenstedt' via blink-dev <blin...@chromium.org> wrote:
I get some of these notifications as well, and I always archive them without reading. That's because unless I were to process all of them carefully, there's little chance that the ones I look at are the most important test failures to investigate.What I'd find useful is an easy way to list all problems relating to LayoutTests/external/wpt/foo, combining TestExpectations, W3CImportExpectations and -expected.txt files. On top of that, maybe something like the Blink bug status mails with links to click through to details.At some point there may be parts of the test suite that are so green that reacting to each new failure makes sense, and then perhaps opting in to notifications like these would be useful.
On Tue, Sep 5, 2017 at 9:39 PM Domenic Denicola <d...@domenic.me> wrote:
+ricea@ and I help maintain the streams/ directory. I think we generally find them a bit spammy (but not horribly so). Some main reasons are:
* Mostly they just notify us of changes that we ourselves made upstream via GitHub. So this doesn't help us much.
* What I really care about is whether any of the imported tests are marked as failing. Figuring this out takes extra work to dig into the CL and find -expected.txt files or changes.
* Most of the emails are bots talking to themselves and approving each other. Generally you get 6 emails for any given import: 3 from "Blink WPT Bot (Gerrit)", 2 from "Commit Bot (Gerrit)", and then one from "Quinten Yearsley (Gerrit)". Only the first of those emails has useful content.
So indeed something like an email summarizing successful imports, especially if it highlighted newly-failing tests with easily clickable links to the -expected.txt files, would be better.
--
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.
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/BLUPR0501MB8523FC3DA834E5C59765206DF960%40BLUPR0501MB852.namprd05.prod.outlook.com.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/97bf99ff-b61d-45d9-993d-5089858328ac%40chromium.org.
I'd prefer a new bug per test. The failing bugs should be added as blocking bugs to a per-directory tracking bug. I prefer individual bugs to replies so it's easier to track and prioritize the effort of fixing each test. I'd be willing to own and review such bugs for IndexedDB.
IndexedDB/
new tests:a.html pass: 30 fail: 2b.html pass: 32deleted tests:c.html
existing tests:d.html pass: 10 (-2) fail: 2 (+2)e.html pass: 6 (+5) fail: 0 (-5)
FWIW our plan with the in-development new import/export process for gecko is to create one bug per upstream PR, with a component determined by the files changed, and give a summary of the changed results on import there. I don't quite know if it will work yet, but it seems at least plausible. Having cross-comparison results from other browsers would be nice, but a little tricky since the bug will typically be created before the PR lands. We could update later or uses the results from travis, but I expect that won't make the first cut.
--
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.
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/28ae5688-442e-4f6d-9aa2-57ca3334838e%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/ecosystem-infra/CAOPAaNLPWb4UaKCZXp2LVRUisQ4SwpHTyWVvvKS6oWfVnzKuCQ%40mail.gmail.com.