+++ This bug was initially created as a clone of Bug #1335799 +++ I'm filing this as a placeholder bug for the next webrender update. I will 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. 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"
For reference, the script I'm using to do this is at https://github.com/staktrace/moz-scripts/blob/master/try-latest-webrender.sh And here's the first try job (not yet on cron, just making sure the setup works): https://treeherder.mozilla.org/#/jobs?repo=try&revision=50a80fc8d87ef42b7492bbc775ab6cb49a4bb18e I have a complicated half-baked idea involving ifdefs and bug numbers to keep our in-tree bindings patched as we encounter changes on the webrender side, so that we can continue to catch additional changes/breakages rather than stopping after the first one. We can jump over that bridge when we get there though.
Jeff said he wanted to update webrender. We can use 938b32ca93bf5e878422ac4bafcdd53f8058f880 since we know it's safe and has the changes he wants.
Assignee: nobody → bugmail
Summary: Future webrender update bug → Update webrender to 938b32ca93bf5e878422ac4bafcdd53f8058f880
Pushed by email@example.com: https://hg.mozilla.org/projects/graphics/rev/c8873c351679 Update webrender to cset 938b32ca93bf5e878422ac4bafcdd53f8058f880. rs=jrmuizel
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
3 years ago
Target Milestone: --- → mozilla54
You need to log in before you can comment on or make changes to this bug.