Platform/GFX/Quantum Render: Difference between revisions

→‎Try pushes: Update WR syntax to an alternative that is easier to escape
(removed link that wasnt needed)
(→‎Try pushes: Update WR syntax to an alternative that is easier to escape)
Line 145: Line 145:
   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]
   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]


You can also run WebRender's standalone tests on tryserver (linting and Linux/Windows tests only for now, macOS is tracked in {{bug|1516568}}). As trychooser syntax is deprecated, the way to run these tests is to select them in <tt>./mach try fuzzy</tt> with the query string <tt>'webrender !docker</tt>. You can do this on the command line like so (the extra quotes are needed to get around <tt>bash</tt> escaping and history expansion metacharacters, and may not be necessary in other shells):
You can also run WebRender's standalone tests on tryserver (linting and Linux/Windows tests only for now, macOS is tracked in {{bug|1516568}}). As trychooser syntax is deprecated, the way to run these tests is to select them in <tt>./mach try fuzzy</tt> with the query string <tt>^webrender-</tt>. You can do this on the command line like so:
   ./mach try fuzzy -q "'"'webrender !docker'
   ./mach try fuzzy -q '^webrender-'


To run all of the QuantumRender tests as well as the WebRender standalone tests, you can use the following command:
To run all of the QuantumRender tests as well as the WebRender standalone tests, you can use the following command:
   ./mach try fuzzy -q "'-qr" -q "'"'webrender !docker'
   ./mach try fuzzy -q "'-qr" -q '^webrender-'
or without talos/raptor:
or without talos/raptor:
   ./mach try fuzzy -q "'"'-qr !talos !raptor' -q "'"'webrender !docker'
   ./mach try fuzzy -q "'"'-qr !talos !raptor' -q '^webrender-'


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:
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:
Confirmed users
586

edits