Ensure MOZ_WEBRENDER is always respected for testing correctness
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
People
(Reporter: kats, Unassigned, NeedInfo)
References
Details
Spinoff from https://bugzilla.mozilla.org/show_bug.cgi?id=1642308#c18
Seems like at some point we allowed WebRender to get enabled even if MOZ_WEBRENDER=0 was in the environment. This means that some test configurations might get run with WR enabled instead of disabled.
|
||
Comment 1•4 years ago
|
||
The severity field is not set for this bug.
:jimm, could you have a look please?
For more information, please visit auto_nag documentation.
|
||
Updated•4 years ago
|
|
||
Updated•4 years ago
|
|
||
Comment 2•4 years ago
|
||
I encountered the opposite problem where we got MOZ_WEBRENDER=1, and an init failure caused us to fallback to basic, and continues with the test and gives misleading results. See bug 1677094. I don't think it is related since we never fallback to turning WebRender on. I am adding gtests that verify the envvars (should) work as expected in that bug however.
|
||
Updated•1 year ago
|
Description
•