+++ This bug was initially created as a clone of Bug #1492389 +++ I'm filing this as a placeholder bug for the next webrender update. I may be running a cron script [1] 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". [1] https://github.com/staktrace/moz-scripts/blob/master/try-latest-webrender.sh

Pushed by jmuizelaar@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/14c6b338e32c Update webrender to f17f6a491d6ff3dc3e13e998dda788d8f5856338

I didn't realize the previous update had been backed out. So I've made a mess of things...

Pushed by jmuizelaar@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/25b839b8e6a9 Adjust test expectations for https://github.com/servo/webrender/pull/3073

Pushed by jmuizelaar@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/6ec508b8d47b Increase the fuzz some more so that things pass.

https://hg.mozilla.org/mozilla-central/rev/14c6b338e32c https://hg.mozilla.org/mozilla-central/rev/25b839b8e6a9 https://hg.mozilla.org/mozilla-central/rev/6ec508b8d47b