Closed
Bug 1550156
Opened 5 years ago
Closed 5 years ago
Expose reason for not getting WebRender in telemetry
Categories
(Core :: Graphics: WebRender, enhancement, P3)
Core
Graphics: WebRender
Tracking
()
RESOLVED
FIXED
mozilla68
| Tracking | Status | |
|---|---|---|
| firefox68 | --- | fixed |
People
(Reporter: jrmuizel, Assigned: aosmond)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
No description provided.
|
Reporter | |
Updated•5 years ago
|
Priority: -- → P3
|
|
Reporter | |
Comment 1•5 years ago
|
||
We have D3D11_COMPOSITING_FAILURE_ID and OPENGL_COMPOSITING_FAILURE_ID for this. We could add a WEBRENDER_COMPOSITING_FAILURE_ID or do something less hacky and adjust the gfx feature stuff to do a better job reporting it's reason for failure.
|
Assignee | |
Updated•5 years ago
|
Assignee: nobody → aosmond
|
|
Assignee | |
Comment 2•5 years ago
|
||
|
||
Updated•5 years ago
|
Blocks: wr-telemetry
Type: defect → enhancement
Pushed by aosmond@gmail.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/2b0e7375950d
Add richer set of gfx feature failure codes for WebRender. r=jrmuizel
|
||
Comment 4•5 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox68:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
|
|
Reporter | |
Comment 5•5 years ago
|
||
I think we broke this with the switch to using the blocklist. We should try to get it back.
Flags: needinfo?(aosmond)
|
|
Assignee | |
Updated•3 years ago
|
Flags: needinfo?(aosmond)
You need to log in
before you can comment on or make changes to this bug.
Description
•