Closed
Bug 1497829
Opened 6 years ago
Closed 6 years ago
Update webrender to 1396114d80fb19df2295a40b0b14abc8f24afa03
Categories
(Core :: Graphics: WebRender, enhancement, P3)
Tracking
()
RESOLVED
FIXED
mozilla64
Tracking | Status | |
---|---|---|
firefox64 | --- | fixed |
People
(Reporter: jan, Assigned: jrmuizel)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [gfx-noted])
+++ This bug was initially created as a clone of Bug #1497768 +++
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/5cd5bff6c91e
Update webrender to commit 1396114d80fb19df2295a40b0b14abc8f24afa03
Reporter | ||
Updated•6 years ago
|
Alias: wr-future-update
Assignee: nobody → jmuizelaar
Summary: Future webrender update bug → Update webrender to 1396114d80fb19df2295a40b0b14abc8f24afa03
Comment 2•6 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
You need to log in
before you can comment on or make changes to this bug.
Description
•