Update webrender to 69dae1fe743bf3656d532672366e7193b041b6f7

RESOLVED FIXED in Firefox 63

Status

()

enhancement
P3
normal
RESOLVED FIXED
Last year
11 months ago

People

(Reporter: darkspirit, Assigned: jrmuizel)

Tracking

(Blocks 2 bugs)

63 Branch
mozilla63
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox63 fixed)

Details

(Whiteboard: [gfx-noted], )

+++ This bug was initially created as a clone of Bug #1486405 +++

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/595a9385a0b0
Update webrender to 69dae1fe743bf3656d532672366e7193b041b6f7
https://hg.mozilla.org/integration/mozilla-inbound/rev/82efdb13962c
Update tests for WebRender changes.
Blocks: 1487588
Alias: wr-future-update
https://hg.mozilla.org/mozilla-central/rev/595a9385a0b0
https://hg.mozilla.org/mozilla-central/rev/82efdb13962c
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
Assignee: nobody → jmuizelaar
No longer blocks: 1487588
Summary: Future webrender update bug → Update webrender to 69dae1fe743bf3656d532672366e7193b041b6f7
Blocks: 1486308
Depends on: 1487915
Depends on: 1487984
Depends on: 1488271
Depends on: 1488713
Depends on: 1489644
You need to log in before you can comment on or make changes to this bug.