Bug 207475 - [ews] Notify bot watchers about pre-existing and flaky test failures found on ews bots
Summary: [ews] Notify bot watchers about pre-existing and flaky test failures found on...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Aakash Jain
URL:
Keywords: InRadar
Depends on: 214670
Blocks:
  Show dependency treegraph
 
Reported: 2020-02-10 10:07 PST by Ryan Haddad
Modified: 2020-09-04 05:09 PDT (History)
6 users (show)

See Also:


Attachments
Patch (5.13 KB, patch)
2020-07-23 08:35 PDT, Aakash Jain
no flags Details | Formatted Diff | Diff
Patch (9.22 KB, patch)
2020-07-23 12:45 PDT, Aakash Jain
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Haddad 2020-02-10 10:07:15 PST
[ews-build] Create a mechanism to notify interested parties about pre-existing test failures found on bots
Comment 1 Radar WebKit Bug Importer 2020-02-10 10:07:35 PST
<rdar://problem/59314769>
Comment 2 Aakash Jain 2020-07-23 08:35:12 PDT
Created attachment 405040 [details]
Patch
Comment 3 Aakash Jain 2020-07-23 12:45:08 PDT
Created attachment 405067 [details]
Patch
Comment 4 Jonathan Bedard 2020-07-23 14:39:35 PDT
Comment on attachment 405067 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=405067&action=review

> Tools/BuildSlaveSupport/ews-build/steps.py:1871
> +                self.send_email_for_flaky_failure(flaky_failure)

Do we have any understanding of how much email this is going to generate?

Seems like it would be a ton. Are the recipients prepared for that?

> Tools/BuildSlaveSupport/ews-build/steps.py:2006
> +    def send_email_for_pre_existing_failure(self, test_name):

This seems way more useful then the flaky one at the moment, because there will be far less of them

> Tools/BuildSlaveSupport/ews-build/steps_unittest.py:1745
> +    def test_flaky_failures_in_first_run(self):

What's the point of this test if we aren't testing the email sending in some way?
Comment 5 Aakash Jain 2020-07-23 14:50:02 PDT
Comment on attachment 405067 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=405067&action=review

>> Tools/BuildSlaveSupport/ews-build/steps.py:1871
>> +                self.send_email_for_flaky_failure(flaky_failure)
> 
> Do we have any understanding of how much email this is going to generate?
> 
> Seems like it would be a ton. Are the recipients prepared for that?

We created a new email address to receive these emails see: https://trac.webkit.org/changeset/264779/webkit

Number of emails would vary based on how many flaky tests or pre-existing failures are there on a given day on trunk. We started these emails today, and we got 35 emails (26 for flaky tests and 9 for pre-existing test failures) so far.

>> Tools/BuildSlaveSupport/ews-build/steps_unittest.py:1745
>> +    def test_flaky_failures_in_first_run(self):
> 
> What's the point of this test if we aren't testing the email sending in some way?

This test is independent of this patch. I could have added it in a separate patch.
Comment 6 Jonathan Bedard 2020-07-23 15:03:02 PDT
Comment on attachment 405067 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=405067&action=review

>>> Tools/BuildSlaveSupport/ews-build/steps.py:1871
>>> +                self.send_email_for_flaky_failure(flaky_failure)
>> 
>> Do we have any understanding of how much email this is going to generate?
>> 
>> Seems like it would be a ton. Are the recipients prepared for that?
> 
> We created a new email address to receive these emails see: https://trac.webkit.org/changeset/264779/webkit
> 
> Number of emails would vary based on how many flaky tests or pre-existing failures are there on a given day on trunk. We started these emails today, and we got 35 emails (26 for flaky tests and 9 for pre-existing test failures) so far.

Does that mean we already have a version of this deployed?
Comment 7 Aakash Jain 2020-07-23 15:07:21 PDT
(In reply to Jonathan Bedard from comment #6)
> Does that mean we already have a version of this deployed?
Yeah
Comment 8 EWS 2020-07-23 15:20:28 PDT
Committed r264795: <https://trac.webkit.org/changeset/264795>

All reviewed patches have been landed. Closing bug and clearing flags on attachment 405067 [details].