WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
207475
[ews] Notify bot watchers about pre-existing and flaky test failures found on ews bots
https://bugs.webkit.org/show_bug.cgi?id=207475
Summary
[ews] Notify bot watchers about pre-existing and flaky test failures found on...
Ryan Haddad
Reported
2020-02-10 10:07:15 PST
[ews-build] Create a mechanism to notify interested parties about pre-existing test failures found on bots
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
Show Obsolete
(1)
View All
Add attachment
proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1
2020-02-10 10:07:35 PST
<
rdar://problem/59314769
>
Aakash Jain
Comment 2
2020-07-23 08:35:12 PDT
Created
attachment 405040
[details]
Patch
Aakash Jain
Comment 3
2020-07-23 12:45:08 PDT
Created
attachment 405067
[details]
Patch
Jonathan Bedard
Comment 4
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?
Aakash Jain
Comment 5
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.
Jonathan Bedard
Comment 6
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?
Aakash Jain
Comment 7
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
EWS
Comment 8
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]
.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug