Changes

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 linux64 QuantumRender-enabled builds, you could use this trychooser syntax: try: -b do -p linux64 ,win64 -u all[linux64-qr,windows10-64-qr] -t all[linux64-qr,windows10-64-qr]

Note here that the build platform is platforms are <tt>linux64</tt> and <tt>win64</tt> but the test platform is platforms are <tt>linux64-qr</tt>. Note also that tests are currently only running on linux64and <tt>windows10-64-qr, so make sure to include that test platform if you want test coverage. Testing on Windows is currently not as easy - we don't have the platform set up in automation yet, so the best way to do a sanity check on Windows is to do a normal Windows try push, but with webrender force-enabled, and then check to make sure it doesn't blow up. You can do this by importing the patch at https:<//hg.mozilla.org/try/rev/3a6b64c653c7dd6e482c02a43b81e5ea10000b06 and applying it as the tipmost patch in your try push. It just flips the gfx.webrender.enabled pref to on by default, and the commit message has the try syntax needed to run debug/opt e10s reftests on Windows. Note that the reftests are *expected* to fail, but if you see crashes (usually due to shader compilation failures or asserts in webrender) then that's a problem you should look intott>.