Changes

Jump to: navigation, search

Platform/GFX/Quantum Render

268 bytes removed, 14:35, 5 July 2019
On reftests: Tweak docs
=== On reftests ===
Many of the existing gecko reftests (over 13000 of them) are passing with Quantum Render. However, there are still around 140 80 failing reftests. These are listed in [https://docs.google.com/spreadsheets/d/1DcqaMvt3I38HIl3-RDS_6aiX67nQWItNcwmVt5utbDk/edit?usp=sharing this Google sheet]. You're welcome to work on getting these passing - please follow the procedure below:
* Identify a single reftest you wish to work on. Try to pick one that sounds unrelated to other reftests that people are working on, because often one patch will fix multiple related reftests.
* File a bug for that reftest, and mark it as blocking {{bug|1322815}} (webrender-reftests).
* Work on the fix. The best way to do this is to remove the fails-if or skip-if annotation in your local checkout and run the reftest using <tt>mach reftest--enable-webrender</tt>. Debug and fix as needed. Note that you can likely work on the bug on Windows/OS X locally, but we only run the tests on Linux64 in automation. So for best results, prefer working on Linux locally when possible.* If you need to do try pushes, use syntax <tt>try: -b do -p linux64 -u all[linux64-qr] -t none</tt>. You should do at least one try push after writing your fix to verify it works in automation, as well as to identify any other tests that are fixed by your patch. Make sure to update the annotations for all newly-passing tests as part of your final commit. Try not to introduce regressions, although breaking a small number of tests to make a larger number pass might be acceptable.
* Land your fix after getting review as appropriate.
Confirm
586
edits

Navigation menu