in or ongoing work to get our linux tests running in taskcluster, we have to build an OS image that supports running tests- all inside of docker. This means a lot of random tweaking to the OS and packages. We see a few consistent failures, specifically some from chunk 8: https://treeherder.mozilla.org/#/jobs?repo=try&revision=899f61b37a6b&group_state=expanded&selectedJob=14965114&filter-searchStr=web TEST-UNEXPECTED-PASS | /webgl/bufferSubData.html | bufferSubData - expected FAIL TEST-UNEXPECTED-PASS | /webgl/compressedTexImage2D.html | compressedTexImage2D - expected FAIL TEST-UNEXPECTED-PASS | /webgl/compressedTexSubImage2D.html | compressedTexSubImage2D - expected FAIL TEST-UNEXPECTED-PASS | /webgl/texImage2D.html | texImage2D - expected FAIL TEST-UNEXPECTED-PASS | /webgl/texSubImage2D.html | texSubImage2D - expected FAIL TEST-UNEXPECTED-PASS | /webgl/uniformMatrixNfv.html | Should not throw for 2 - expected FAIL TEST-UNEXPECTED-PASS | /webgl/uniformMatrixNfv.html | Should not throw for 3 - expected FAIL TEST-UNEXPECTED-PASS | /webgl/uniformMatrixNfv.html | Should not throw for 4 - expected FAIL we have upgraded the mesa driver (bug 1220658) in the docker image, and have yet to do it on the buildbot based ec2 vms. That is in progress, but not ready to go yet. When we upgraded on docker, we had to skip some tests as they were unexpected-pass in the mochitest-gl job. Most likely that is the case here, and ideally we will resolve this as part of the mesa driver, otherwise- we will have to look into it via other methods.

Skipping tests seems like the wrong thing to do. They should have the expectation marked according to what is actually expected.

well we have expected-fail on the old driver and expected-pass with the new driver- and we had no roadmap to upgrade both at the same time- so for now it is skip with a bug pending on the mesa driver upgrade to fix the manifest.

the same tests are failing on m-c: https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&revision=ec3eeea80a5e&filter-searchStr=Linux%20x64%20opt%20W3C%20Web%20Platform%20Tests%20W3C%20Web%20Platform%20Tests%20W%284%29&group_state=expanded&selectedJob=2980704 so far this looks to be the only fallout!

hmm, it looks as though the mesa driver was backed out, most likely we will need to do the same on taskcluster which would make this bug invalid.

At least we know the path forward for taskcluster. Maybe at this rate we can just wait until tests are running in taskcluster?

I would like to back out the mesa driver for the taskcluster image so we can get green tests on web-platform-tests and start running those side by side. If it takes 2 months to get mesa live, then we will always have tests which we cannot run side by side in production. The goal is to get 100% side by side. I am open to other viewpoints or reasoning.

Works for me.

I backed out the mesa changes late last week. What's next?

theoretically wpt-8 should be green, I think this bug should be closed. There we always the same 6 errors, and I verified in the short while that we had the new mesa driver on buildbot that we got the same 6 errors. I say close this.

Downgrading mesa got this green.