Closed Bug 1493473 Opened 6 years ago Closed 6 years ago

Update webrender to 4e7d0ed1b08f5402a6971230864a7e497b2453ec

Categories

(Core :: Graphics: WebRender, enhancement, P3)

Product:
Core
Component:
Graphics: WebRender
Version:
64 Branch
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla64
Tracking Flags:
Tracking Status
firefox64 --- fixed

People

(Reporter: jrmuizel, Assigned: jrmuizel)

References

(
URL
)

Details

(Whiteboard: [gfx-noted]) 

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

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

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
No longer depends on: 1493268
No longer blocks: 1477819, 1493068, 1493273
Blocks: 1493177
Pushed by jmuizelaar@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/5c2a8331f82c
Update webrender to 4e7d0ed1b08f5402a6971230864a7e497b2453ec
Alias: wr-future-update
Assignee: nobody → jmuizelaar
URL: https://github.com/servo/webrender/co...
Summary: Future webrender update bug → Update webrender to 4e7d0ed1b08f5402a6971230864a7e497b2453ec
https://hg.mozilla.org/mozilla-central/rev/5c2a8331f82c
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox64: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
You need to log in before you can comment on or make changes to this bug.