Open
Bug 1379911
Opened 7 years ago
Updated 2 years ago
Device Reset Testing.
Categories
(Core :: Graphics, enhancement, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox57 | --- | fix-optional |
People
(Reporter: vliu, Unassigned)
Details
(Whiteboard: [gfx-noted])
Attachments
(2 files)
14.00 KB,
patch
|
Details | Diff | Splinter Review | |
2.59 MB,
patch
|
Details | Diff | Splinter Review |
This bug was filed intending to implement test cases for device reset. Basically this idea was raised when we found a way to trigger device removed event manually. in [1], the session *Testing Device Removed Handling* mentioned how it did. Based on above, it would be better if we can have test cases to hook up dxcap with animation or video cases. [1]: https://docs.microsoft.com/en-us/windows/uwp/gaming/handling-device-lost-scenarios
Reporter | ||
Updated•7 years ago
|
Assignee: nobody → vliu
Reporter | ||
Comment 1•7 years ago
|
||
There were some known issues to note. 1. To run dxcap, the execution shell need to have administrator access. 2. The whole windows operating system was easily to crash if dxcap was run too much frquently. I am looking into the code in crashtest framework. Currently my idea would be. 1. a parameter in test case in crashtests.list to specifiy which test case will run device test testing. 2. Test cases was considered to cover video/animation. At this moment I don't rule out using other known test cases to do this. I just start with crash test.
Reporter | ||
Comment 2•7 years ago
|
||
The first version of WIP was attached to record. In this WIP, we can run dxCap.exe in specific crash test if it was defined by the keyword |device-reset| in crashtests.list. I also wrote two use cases for animation/video. It seems it still have problems for running animation/video, so I still working on it.
Reporter | ||
Comment 3•7 years ago
|
||
Another WIP was attached to attempt run dxCap on try server. See [1] for detail. [1]: https://treeherder.mozilla.org/#/jobs?repo=try&revision=9824ff2928e2a7235ea5ce597b3f013208c8c1cf&selectedJob=115890579 From [1], when test case tried to access dxCap to run, it always returns NS_ERROR_FILE_NOT_FOUND. It could be incorrect path or doesn't have this execution file. 02:27:02 INFO - REFTEST INFO | device-reset: RunDxCap 02:27:02 INFO - JavaScript error: chrome://reftest/content/reftest.jsm, line 1332: NS_ERROR_FILE_NOT_FOUND: Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIProcess.init]
Updated•7 years ago
|
status-firefox57:
--- → fix-optional
Updated•7 years ago
|
Priority: -- → P3
Whiteboard: [gfx-noted]
Comment 4•2 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Assignee: vincent.liu1013 → nobody
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•