Add testing variant for disabling GPU process
Categories
(Core :: Graphics, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox133 | --- | fixed |
People
(Reporter: bradwerth, Assigned: bradwerth)
References
(Blocks 3 open bugs)
Details
Attachments
(3 files, 1 obsolete file)
An isolated GPU process is currently on-by-default for Windows and Android, and available but off-by-default for Linux X11. As we expand this capability to more platforms, and change the feature to on-by-default on more platforms, it will be useful to have a test variant that can compare test behavior with or without the isolated GPU process. Since the goal is to have GPU process on-by-default for all platforms, the variant should probably be a "no-gpu-process" variant that will eventually be removed once the feature is mature.
| Assignee | ||
Comment 1•2 years ago
|
||
This allows us to test platforms that support GPU process without
enabling the GPU process. It may help us flush out differing test
outcomes between the two cases. Eventually this will be retired when all
platforms have mature GPU process implementations.
| Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 3•2 years ago
|
||
Backed out for causing mochitest mda perma failures + reftest failures
Backout link: https://hg.mozilla.org/integration/autoland/rev/105391056fe502d3a27b698eb0239b85693b334e
Comment 5•2 years ago
•
|
||
Backed out for causing failures at UtilityProcessManager.cpp.
Backout link: https://hg.mozilla.org/integration/autoland/rev/28cd4bcb06170c48fb041cbd4a7fc5a50897e5ef
Push where failures started: https://treeherder.mozilla.org/jobs?repo=autoland&selectedTaskRun=a0xM66GuQvuRjJcMNSXmhg.0&resultStatus=testfailed%2Cbusted%2Cexception&revision=1dc5ccccdeae3b472fd5ef136e875fbebd5ab046
Failure log: https://treeherder.mozilla.org/logviewer?job_id=475039852&repo=autoland&lineNumber=2191
| Assignee | ||
Comment 6•2 years ago
|
||
At some point, UtilityAudioDecoderChild lost the ability to work
without a GPU process. This patch remedies that by creating an
alternate connection for the endpoint, modeled after the code in
RDDProcessManager.
Updated•2 years ago
|
Comment 8•2 years ago
•
|
||
Backed out for causing multiple R-nogpu failures
The failures can be seen in the above link. The tier 2 ones seem to be failing the same on each push.
| Assignee | ||
Comment 9•2 years ago
|
||
Allowing (once again) a no-gpu-process option increases the number of
pixels which get antialiased differently than the reference image. The
images continue to largely match; it's just an increase in the number of
close-but-not-quite pixels.
Comment 10•2 years ago
|
||
Comment 11•2 years ago
•
|
||
Backed out for causing multiple reftest failures on multiple platforms with no-gpu enabled flavors.
To check all the failures caused by this, please visit this link -> it has a filter that shows all the failures marked as fix by commit with this backout.
- Backout link
This also caused Bug 1920837 and Bug 1920839, this bugs are closed after the backout.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 12•2 years ago
|
||
Comment 13•2 years ago
|
||
Backed out for causing refetest failures.
Backout link: https://hg.mozilla.org/integration/autoland/rev/9ad4972f496a5553570d2e665a33d75e17ba44ff
Failures started here: https://treeherder.mozilla.org/jobs?repo=autoland&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel&searchStr=reftest&revision=ea17a1d18e7dec25c08dd1eba7fb3b985fc0861e
Failure log: https://treeherder.mozilla.org/logviewer?job_id=475839772&repo=autoland&lineNumber=14617
Comment 14•2 years ago
|
||
Comment 15•2 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/ea1c122a3848
https://hg.mozilla.org/mozilla-central/rev/226668ab3f35
https://hg.mozilla.org/mozilla-central/rev/bd7b34ae33ef
| Assignee | ||
Comment 16•2 years ago
|
||
Hopefully this one will stick, thank you all for your patience on this.
Comment 17•2 years ago
|
||
Backed out for causing multiple nogpu reftest failures.
You can check the failures in this link
Comment 18•2 years ago
|
||
Backout merged to central: https://hg.mozilla.org/mozilla-central/rev/9354af15899d
Comment 19•2 years ago
|
||
Comment 20•2 years ago
|
||
Backed out for causing no-gpu related reftests failures.
- Backout link
- Push with failures
- Failure Log
- Failure line: REFTEST TEST-UNEXPECTED-PASS | layout/reftests/bugs/1412375.html == layout/reftests/bugs/1412375-ref.html | image comparison, max difference: 0, number of differing pixels: 0
Comment 21•2 years ago
|
||
Comment 22•2 years ago
|
||
Backed out for causing multiple no-gpu reftest failures.
Same issues as the backouts that I've made before.
Updated•2 years ago
|
Comment 23•2 years ago
|
||
Comment 24•2 years ago
|
||
Backed out for causing nogpu related reftests failures.
- Backout link
- Push with failures
- Failure Log
- Failure line: REFTEST TEST-UNEXPECTED-FAIL | layout/reftests/bugs/1840511-2.html == layout/reftests/bugs/1840511-1-ref.html | image comparison, max difference: 1, number of differing pixels: 309
| Assignee | ||
Comment 25•2 years ago
|
||
Apologies to the sheriffs and to anybody else watching this Bug or waiting for it to land. The failures are already filed as intermittents, but it's not acceptable to turn them into perma-fails by landing this Bug. I should have understood that sooner; I'm sorry! There's a couple of things I'll have to do differently to make this landable. Here's what I've realized about the test failures that keep bouncing this Bug:
- Some tests already in the tree behave very differently with and without a gpu process. Since some platforms have one and some don't, this is expressed as very complex
fuzzy-ifdeclarations. A declaration like this is trying to tease out whether or not a gpu process is in use. The changes in this Bug are altering those conditions, which is leading to failures in tests. - The intermittent Bugs already filed on some of the affected tests are needed because sometimes these tests downgrade to abandon the gpu process after enough crashes in the process. So if a test is run after the gpu process is abandoned, it'll have a very different outcome. Bug 1895731 is an example. Without a gpu process, it draws nothing at all. This sometimes happen even on platforms with a gpu process, thus the intermittent.
So what to do about this? The ideal would be to update the sandbox with a variable indicating whether or not there is a gpu process in use. Unfortunately, the presence of the gpu process is not exposed to JS and I'm not sure how to do that. An alternative would be to add a variable that indicates whether a gpu process is possible (based on prefs and our current platform support) which will be mostly the same. Such a variable would be useful in simplifying the fuzzy-if logic for Case 1, above. It won't help with the Case 2 intermittents.
So that's what I'm going to do. I'll add nogpu as a variable to the sandbox and fuzz or disable tests that behave very differently with that variable set to true. It will be temporarily annoying to have a variable expressing the absence of something, but as every platform is expected to support a gpu process in time, then this variable and all the annotations around it will eventually be removed.
Comment 26•2 years ago
|
||
Comment 27•2 years ago
•
|
||
Backed out for causing reftest failures on background-blending-color.html
[task 2024-10-08T17:54:45.091Z] 17:54:45 INFO - REFTEST TEST-START | layout/reftests/css-blending/background-blending-color.html == layout/reftests/css-blending/background-blending-color-ref.svg
[task 2024-10-08T17:54:45.091Z] 17:54:45 INFO - REFTEST TEST-LOAD | http://10.0.2.2:8854/tests/layout/reftests/css-blending/background-blending-color.html | 61 / 1022 (5%)
[task 2024-10-08T17:54:45.091Z] 17:54:45 INFO - REFTEST TEST-LOAD | http://10.0.2.2:8854/tests/layout/reftests/css-blending/background-blending-color-ref.svg | 61 / 1022 (5%)
[task 2024-10-08T17:54:45.091Z] 17:54:45 INFO - REFTEST INFO | REFTEST wr-on-android dropping fuzz of (1, 9600) to (0, 0)
[task 2024-10-08T17:54:45.092Z] 17:54:45 INFO - REFTEST INFO | REFTEST fuzzy test (1, 8000) <= (0, 0) <= (1, 9600)
[task 2024-10-08T17:54:45.092Z] 17:54:45 WARNING - REFTEST TEST-UNEXPECTED-PASS | layout/reftests/css-blending/background-blending-color.html == layout/reftests/css-blending/background-blending-color-ref.svg | image comparison, max difference: 0, number of differing pixels: 0
<...>
[task 2024-10-08T17:54:45.135Z] 17:54:45 INFO - REFTEST TEST-END | layout/reftests/css-blending/background-blending-color.html == layout/reftests/css-blending/background-blending-color-ref.svg
Comment 28•2 years ago
|
||
Comment 29•2 years ago
|
||
Comment 30•2 years ago
|
||
Backed out for causing reftest failures on 1412375.
Failure log: https://treeherder.mozilla.org/logviewer?job_id=477481117&repo=autoland
Backout link: https://hg.mozilla.org/integration/autoland/rev/8a1fa23df5f998a79ab500c157ed3150ad1b163e
Comment 31•2 years ago
|
||
fuzzy-if((!nogpu&&....
on the failing test. Did you mean to have the ! in there?
Comment 32•2 years ago
|
||
Comment 33•2 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/90218d9fb410
https://hg.mozilla.org/mozilla-central/rev/c8be4eae972c
https://hg.mozilla.org/mozilla-central/rev/5c17ec5dca7b
Comment 35•1 year ago
|
||
Comment 36•1 year ago
|
||
Comment on attachment 9466114 [details]
Bug 1919114. Extend expiration of no-gpu-process variant. r?#gfx-reviewers
Revision D238163 was moved to bug 1948189. Setting attachment 9466114 [details] to obsolete.
Description
•