On Sep 30, 2019, at 9:32 AM, Adrian Perez de Castro <aperez@igalia.com> wrote:
Hello Aakash (and everybody else),
On Thu, 26 Sep 2019 14:27:25 -0400, Aakash Jain <aakash_jain@apple.com> wrote:
I have been making number of improvements to EWS. I also have various planned improvements to EWS […]
Thanks once again for your continued work on improving the EWS, it is much appreciated =)
Thank You for the feedback. I am hoping that Improved EWS would increase overall team's productivity as people have to deal less with build/test breakages and rollouts.
Here is the list of improvements (in no particular order):
[…]
3) Add a way to retry a patch in EWS. This would allow engineers to confirm that the failures indicated by EWS aren't flaky/incorrect. Maybe a good place to add the 'retry' button would be the status-bubble's tool-tip (visible only if the bubble is red) https://webkit.org/b/196599 <https://webkit.org/b/196599>
Being able to retry a patch without having to re-upload it, and more importantly without having to ping another person, would be neat. I don't have a strong opinion about which tasks to prioritize first, tho.
[…]
6) Add more test-suites to EWS (e.g.: LLDB tests, resultsdbpy tests) https://webkit.org/b/189206 <https://webkit.org/b/189206>, https://webkit.org/b/201928 <https://webkit.org/b/201928>
In this line of adding more things that the EWS could test, among the developers of the GTK/WPE ports we think it would be manageable for us to have bots run API tests. There is some work we need to do, and the intention is to start with GTK first, see how it goes, and then add WPE afterwards. Carlos opened a bug for this, I took the liberty of CC'ing you assuming that you might want to at least keep tabs on it (feel free to unsubscribe):
Sure, I will work with you and Carlos on this.
Best regards, —Adrián