+++ This bug was initially created as a clone of Bug #1480433 +++ I'm filing this as a placeholder bug for the next webrender update. I may be running a cron script  that does try pushes with webrender update attempts, so that we can track build/test breakages introduced by webrender on a rolling basis. This bug will hold the try push links as well as dependencies filed for those breakages, so that we have a better idea going into the update of what needs fixing. I might abort the cron job because once things get too far out of sync it's hard to fully automate fixing all the breakages. When we are ready to actually land the update, we can rename this bug and use it for the update, and then file a new bug for the next "future update".  https://github.com/staktrace/moz-scripts/blob/master/try-latest-webrender.sh
Btw I won't post links like I did before but I'll leave the Cron running and it will do try pushes every 8 hours without applying any additional patches. Might still be useful to quickly narrow down which PRs introduced test failures etc. You can see results at https://firstname.lastname@example.org
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/7846bdd3762c Update webrender to commit 890f3746b798538d201e54b66d2711a70447b781
Summary: Future webrender update bug → Update webrender to commit 890f3746b798538d201e54b66d2711a70447b781
You need to log in before you can comment on or make changes to this bug.