RESOLVED FIXED 200399
New EWS: Notify person on failure
https://bugs.webkit.org/show_bug.cgi?id=200399
Summary New EWS: Notify person on failure
Daniel Bates
Reported 2019-08-02 11:42:25 PDT
Unlike the old EWS the new EWS system does not comment on bugs when a failure occurs. As a result of this lack of bug commenting => there is a lack of bug emails => a person must manually poll each of their bugs to know if the EWS found a problem. Different EWS bots take different lengths of time to process a patch plus patches could be sitting in queues waiting to be processed. Polling for EWS status either is inefficient and wastes many man-hours. (This includes implicit polling by way of leaving the browser window open and glancing at the bubbles every so often). We should add some mechanism (maybe an opt-in registration) for people that want notifications about EWS failures to receive them. Concrete example, I posted a patch for bug #199960 a week ago, forgot about it and thought the reviewers forgot about it. Went to go check that bug today to find that the patch failed on the ios-wk2 EWS bot. Some reviewers are naturally hesitant to review patches that caused EWS failures (there's a lot of reasons why). If I had known days ago about this failure then I would have updated the patch and may have already got it reviewed and landed.
Attachments
Radar WebKit Bug Importer
Comment 1 2019-08-02 11:42:40 PDT
Daniel Bates
Comment 2 2019-08-02 12:08:56 PDT
It would also be cool to be able to opt-in to receive notification on patch failures for bugs **I am interested in**. Old EWS supported this by way of Bugzilla bug mail settings.
Aakash Jain
Comment 3 2019-09-19 09:37:01 PDT
We removed the comments as per the discussion on webkit-dev: https://lists.webkit.org/pipermail/webkit-dev/2019-June/030683.html
Aakash Jain
Comment 4 2019-12-03 04:17:07 PST
I sent out a survey to collect more info about this: https://lists.webkit.org/pipermail/webkit-dev/2019-December/030980.html
Aakash Jain
Comment 5 2020-08-25 09:13:56 PDT
Note You need to log in before you can comment on or make changes to this bug.