Closed Bug 1442422 Opened 6 years ago Closed 6 years ago

Update webrender to 0da6c839b3a0e165f1115fb9fe286be7540c24ed


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

60 Branch



Tracking Status
firefox60 --- fixed


(Reporter: kats, Assigned: kats)



(Whiteboard: [gfx-noted])


(1 file)

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

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".

WR @ 6f6573e7d0662a553902a808d0f837f4c0491244

Many windows webgl mochitest failures

WR @ fc7f59280caf0c18b4de9d5bd480f8ae2c995695


These mochitest failures actually seem to have been introduced by something in the last WR update but have gotten worse here. See for example - the windows webgl mochitests were pretty green (with some blue) until the WR update landed and then we started getting a sprinkling of orange with more heavy blue. But in the above try pushes they're a lot more orange/blue than before.
For the record the move to use a workspace in m-c (bug 1381576) broke my script to do WR updates so that's why there haven't been any pushes since Friday.
WR @ fc7f59280caf0c18b4de9d5bd480f8ae2c995695

Linux seems green, windows seems to have issues. This looks a lot like the mochitest-webgl problems we were having before but this try push includes the workaround patch (which otherwise gets clobbered by the WR update) so in theory it shouldn't have this problem. Not sure what's going on.
WR @ c6ea7526e8fbbcf0596ccd4abf3eb20c9661ebcb

More of the same. Some linux oranges too.

I'm starting to suspect this is coming from servo/webrender#2474. I did a couple more try pushes to check:

Here's one at the same revision currently in m-c, just as a sanity check to make sure the baseline is still good with my script fixes + reapplying the workaround patch

And here's a push with servo/webrender#2474 applied:
Blocks: 1442718
WR @ 4df61ef1eec002c26641e24e5d9a1988d3444793

About the same. Doing a try push now with nical's proper fix from bug 1442748 which should make things green again.
Alias: wr-future-update
Assignee: nobody → bugmail
Summary: Future webrender update bug → Update webrender to 0da6c839b3a0e165f1115fb9fe286be7540c24ed
Version: unspecified → 60 Branch
Comment on attachment 8956836 [details]
Bug 1442422 - Update webrender to commit 0da6c839b3a0e165f1115fb9fe286be7540c24ed.
Attachment #8956836 - Flags: review?(jmuizelaar) → review+
Pushed by
Update webrender to commit 0da6c839b3a0e165f1115fb9fe286be7540c24ed. r=jrmuizel
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla60
You need to log in before you can comment on or make changes to this bug.