+++ This bug was initially created as a clone of Bug #1496171 +++ 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
(In reply to Sotaro Ikeda [:sotaro] from comment #1) > https://github.com/servo/webrender/pull/3170 requests attachment 9014333 [details] [diff] [review] > [details] [diff] [review] in Bug 1461239. Updated to attachment 9014996 [details] [diff] [review].
It looks like this might introduce an intermittent on mochitest-e10s 4 on linux-qr
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/7801a4fb37db Update webrender to 923ee495bd9b0fda8a4a94c5a6cf42e2f0548731 https://hg.mozilla.org/integration/mozilla-inbound/rev/2cee53dd5773 Update layout/reftests/async-scrolling/reftest.list for #3173
Summary: Future webrender update bug → Update webrender to 923ee495bd9b0fda8a4a94c5a6cf42e2f0548731
(In reply to Jeff Muizelaar [:jrmuizel] from comment #4) > It looks like this might introduce an intermittent on mochitest-e10s 4 on > linux-qr It was already intermittent before, bug 1462980. I can look into that.
You need to log in before you can comment on or make changes to this bug.