Enable notifications for new wdspec failures on downstream sync
Categories
(Remote Protocol :: Agent, task, P2)
Tracking
(Not tracked)
People
(Reporter: whimboo, Assigned: whimboo)
References
()
Details
(Whiteboard: [webdriver:m12])
I noticed today when I was CC'ed on bug 1918806 that the wpt sync bot can actually file bugs on Bugzilla to notify about new failures that started with a downstream sync. This is pretty nice because it would allow us to see new failures immediately without forcing me to have to check the metadata changes for each and every downstream sync under testing/web-platform/tests/webdriver/tests and the appropriate Mozilla-specific tests as well.
Given that our tests are correctly tagged in testing/web-platform/moz.build for all of our components under Remote Protocol on Bugzilla, we would only have to add these components in this file:
https://github.com/mozilla/wpt-sync/blob/79399b62e827e697ea572ebd13f4e4133224521f/sync_prod.ini#L103
|
Assignee | |
Comment 1•1 month ago
|
||
I created a PR at https://github.com/mozilla/wpt-sync/pull/2337.
|
|
Assignee | |
Comment 2•1 month ago
|
||
The upstream PR got merged. So I assume that we will get notifications when there are new failing tests starting with the next downstream sync.
|
|
Assignee | |
Comment 3•1 month ago
|
||
Lets check if it works as expected when bug 1919984 gets synced to mozilla-central.
|
||
Comment 4•1 month ago
|
||
The notifications will start working just yet because it requires a deployment of wpt-sync. I'm planning to do it later this week, and I'll update it here when it happens.
Also, a note that notification generation actually happens on the downstream sync stage (not when it lands to gecko), after we get try results for this specific sync, since only at that moment we can determine that test failures are related to this change.
|
|
||
Comment 5•1 month ago
|
||
The new version of wpt-sync bot with updated notification config is deployed.
Description
•