QA/Platform/Graphics/Quantum/Renderer: Difference between revisions

Jump to navigation Jump to search

QA/Platform/Graphics/Quantum/Renderer (view source)

Revision as of 22:20, 3 March 2017

36 bytes added ,  3 March 2017
→‎Automation Review
Line 107: Line 107:
* Currently there are 138 failing reftests as of 2017-03-01 with WebRenderer enabled ([https://docs.google.com/spreadsheets/d/1DcqaMvt3I38HIl3-RDS_6aiX67nQWItNcwmVt5utbDk/edit#gid=0 tracking] - [https://bugzilla.mozilla.org/show_bug.cgi?id=1322815 metabug] - [https://wiki.mozilla.org/Platform/GFX/Quantum_Render#On_reftests wiki] - [https://treeherder.mozilla.org/#/jobs?repo=graphics treeherder]). Once these are fixed we'll want to run all reftests with WebRenderer enabled and with WebRenderer disabled which, since WebRenderer depends on e10s, we'll need to run the reftests 3x (non-e10s, e10s+WR, e10s-WR).  
* Currently there are 138 failing reftests as of 2017-03-01 with WebRenderer enabled ([https://docs.google.com/spreadsheets/d/1DcqaMvt3I38HIl3-RDS_6aiX67nQWItNcwmVt5utbDk/edit#gid=0 tracking] - [https://bugzilla.mozilla.org/show_bug.cgi?id=1322815 metabug] - [https://wiki.mozilla.org/Platform/GFX/Quantum_Render#On_reftests wiki] - [https://treeherder.mozilla.org/#/jobs?repo=graphics treeherder]). Once these are fixed we'll want to run all reftests with WebRenderer enabled and with WebRenderer disabled which, since WebRenderer depends on e10s, we'll need to run the reftests 3x (non-e10s, e10s+WR, e10s-WR).  
* From a platform perspective we will only be concerned with Windows 7 Platform Update and later with D3D11 enabled. This means that, at least for now, we will not need to double-up tests on Mac, Linux, Android, and older Windows environments. However, this also means that we'll have to support doubling-up reftests until such time as we drop support for non-WebRenderer supported hardware/platforms.
* From a platform perspective we will only be concerned with Windows 7 Platform Update and later with D3D11 enabled. This means that, at least for now, we will not need to double-up tests on Mac, Linux, Android, and older Windows environments. However, this also means that we'll have to support doubling-up reftests until such time as we drop support for non-WebRenderer supported hardware/platforms.
* {{bug|1342450}} Build webrenderer on nightly/local builds
 


; Modeling based on e10s
; Modeling based on e10s
Line 115: Line 115:


; Builds
; Builds
Kats added a QR-enabled Linux build on mozilla-central for a subset of gfx tests.
* Kats added a QR-enabled Linux build on mozilla-central for a subset of gfx tests.
* Building WebRenderer on nightly/local builds is in progress via {{bug|1342450}}
* Need to get tests working on Windows


; Tests
; Tests
* [https://searchfox.org/mozilla-central/source/gfx/layers/apz/test/ APZ]
* [https://searchfox.org/mozilla-central/source/gfx/layers/apz/test/ APZ]
* [https://searchfox.org/mozilla-central/source/gfx/tests GFX]
* [https://searchfox.org/mozilla-central/source/gfx/tests GFX]
* Talos?


; Considerations
; Considerations
* Platforms - user platforms vs test platforms
* <u>How long do graphics-related tests take to run on average?</u><br />??? ...checking with catlee... ???
* win32, win32-on-64, win64
* <u>How much overhead will QR tests impose?</u><br />Near-zero
* GPUs
* <u>Which platforms need to be supported</u><br />Initially we only need to support Windows 7 and above.<br />Linux, MacOS, and Android will be added at a later date.
* D3D vs Basic
* <u>Which build types need to be supported</u><br /> ??? ...debug/opt/pgo/asan... ???
* Debug vs Opt vs PGO vs ASAN
* <u>Which hardware needs to be supported<u><br /> ??? ...need to support D3D11+ hardware, if possible... ???
* e10s+WR, e10s-WR, non-e10s
* <u>Which HWA modes need testing?</u><br /> ??? ...QR+D3D | QR+Basic | Gecko+D3D | Gecko+Basic... ???
* how long we plan to support environments where WR is not supported?
* <u>How long will we need to support hardware/platforms unsupported by QR?</u><br /> ...?
* how long we plan to support non-WR under WR-supported environments?
* <u>How long will we need to support Gecko under QR supported platforms/hardware?</u><br /> ...?
* what tests do we need to run, how long do they take, and how much compute time should it cost?
* <u>How much does Bughunter testing cost us and do we need to test in QR/non-QR builds?</u><br /> ...?
* are there tests we don't need to run? are there new tests we need to add?
* <u>How much does performance testing cost us and do we need to test in QR/non-QR builds?</u><br /> ...?
* are there performance tests we need to run in addition to correctness?
* do we only need to run reftests, what about mochitest-gpu/gl?
* I might suggest tracking test coverage/requirements similar to [https://wiki.mozilla.org/Electrolysis/Test_Coverage e10s]


; Fuzzing
; Fuzzing
The Stylo team is working on some fuzzing tests for CSS and DOM APIs, this may or may not be relevant to QR. There are visual reftests of 200+ real websites, comparing screenshots of pages rendered in Gecko with Stylo enabled vs disabled. Shing Lyu and I are working on the real website reftests (in bug 1331552), if you'd like more information.
* QR will do Bughunter testing via {{bug|1336436}}
* QR will do Bughunter testing via {{bug|1336436}}


Ashughes
Confirmed users
14,525

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1164542"

Navigation menu