Closed Bug 1329213 Opened 4 years ago Closed 4 years ago
Stand up more QR automated testing
I did a try push yesterday  for Linux QR builds with all of the possible test suites enabled. There's a lot failing but also some green stuff. We should probably turn on the ones that are already green, to make sure they don't regress. Also adding some of these test suites (e.g. gtests) might be useful in that we can add more tests to them to test things in webrender.  https://treeherder.mozilla.org/#/jobs?repo=try&revision=f221382e008e71bce9594b260753339b3e4a0009
The following suites are fully green: - cppunit - gtest - reftest-no-accel The following seem to be green in non-e10s but orange in e10s, and we can probably get them working without too much trouble (in a follow-up bug): - marionette - web-platform-tests - firefox-ui-functional-local - firefox-ui-functional-remote
Pushed by email@example.com: https://hg.mozilla.org/projects/graphics/rev/e7b1d82db69b Turn on more test suites for the QR build. r=gfx?
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Can someone fill me in on what ‘QR builds’ are?
QR stands for "Quantum Render". They are builds on the graphics branch which include the webrender rust library integrated into gecko.
4 years ago
Target Milestone: --- → mozilla54
You need to log in before you can comment on or make changes to this bug.