Closed
Bug 1493890
Opened 6 years ago
Closed 6 years ago
Update webrender to 2549b791abb3a24c115d03616ddd82e14727b5a1
Categories
(Core :: Graphics: WebRender, enhancement, P3)
Tracking
()
RESOLVED
FIXED
mozilla64
Tracking | Status | |
---|---|---|
firefox64 | --- | fixed |
People
(Reporter: jan, Assigned: jrmuizel)
References
()
Details
(Whiteboard: [gfx-noted])
+++ This bug was initially created as a clone of Bug #1493496 +++ 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
Assignee | ||
Comment 1•6 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=a0f14e20e7b4c8d57cf84f4d8ca69bb1cb759545
Pushed by jmuizelaar@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/3483ad374965 Update webrender to commit 2549b791abb3a24c115d03616ddd82e14727b5a1 https://hg.mozilla.org/integration/mozilla-inbound/rev/470a41de5b5c Adjust for do_aa paramter.
Reporter | ||
Updated•6 years ago
|
Alias: wr-future-update
Assignee: nobody → jmuizelaar
Summary: Future webrender update bug → Update webrender to 2549b791abb3a24c115d03616ddd82e14727b5a1
Comment 3•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/3483ad374965 https://hg.mozilla.org/mozilla-central/rev/470a41de5b5c
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
•