Confirm
586
edits
Changes
→Try syntax: Update try section
MOZ_ACCELERATED=1 MOZ_WEBRENDER=1 ./mach reftest layout/reftests/reftest-sanity/
=== Try syntax pushes ===
You can (and are encouraged to) push changes to tryserver to test them out before landing them. For linux64, the tests will run using a regular linux64 build. However, you need to specify <tt>linux64-qr</tt> as the test platform to have QR enabled during testing. The same goes for windows10-64. So, for example, to run all the available tests on QuantumRender-enabled builds, you could use this trychooser syntax:
try: -b do -p linux64,win64,macosx64 -u all[linux64-qr,windows10-64-qr,macosx64-qr] -t all[linux64-qr,windows10-64-qr,macosx64-qr]
./mach try fuzzy -q "'"'webrender !docker'
or without talos/raptor:
./mach try fuzzy -q "'"'-qr !talos !raptor' -q "'"'webrender !docker'
If you have a particular set of tests you run frequently that cannot be represented by trychooser syntax, the best way to do it is this:
* First, do a push using <tt>./mach try fuzzy</tt> where you select the set of jobs you care about
* The head commit of that try push will have a <tt>try_tasks_config.json</tt> file which lists the jobs. Copy that file into a local commit
* Whenever you want to do a new push with that same set of jobs, cherry-pick or apply that commit as your head commit and just <tt>hg push</tt> or <tt>git push</tt> to try (no need for <tt>./mach try</tt> here).
=== Automation ===
