Perma timeout of TV-nofis [infra, tier 2] dom/media/webrtc/tests/mochitests on android-em-7.0-x86_64-qr/debug-isolated
Categories
(Core :: WebRTC: Audio/Video, defect)
Tracking
()
People
(Reporter: jib, Unassigned)
References
(Depends on 2 open bugs, Blocks 1 open bug)
Details
While landing bug 1528042, mochitests we touched were failing the Test Verify tests on android-em-7.0-x86_64-qr/debug-isolated.
Since unlike most test tasks, TV runs only when tests are modified, and only runs the modified tests, failures are easily mis-attributed to patches that happen to touch the tests in ways that pass on every on other platform. To avoid further confusion, e.g. bug 1528042 comment 22, we'll turn them off for now in bug 1528042, and use this bug to track turning them back on after what seems to be an infra issue.
https://treeherder.mozilla.org/logviewer?job_id=415900306&repo=autoland&lineNumber=2101
04:38:26 WARNING - TEST-UNEXPECTED-FAIL | dom/media/webrtc/tests/mochitests/test_enumerateDevices_legacy.html | application timed out after 370 seconds with no output
2107 04:38:42 WARNING - PROCESS-CRASH | dom/media/webrtc/tests/mochitests/test_enumerateDevices_legacy.html | application crashed [@ __epoll_pwait]
8069 04:38:44 ERROR - No tests run or test summary not found
8191 04:45:37 WARNING - TEST-UNEXPECTED-FAIL | dom/media/webrtc/tests/mochitests/test_getUserMedia_trackCloneCleanup.html | application timed out after 370 seconds with no output
8197 04:45:53 WARNING - PROCESS-CRASH | dom/media/webrtc/tests/mochitests/test_getUserMedia_trackCloneCleanup.html | application crashed [@ __epoll_pwait]
14044 04:45:54 ERROR - No tests run or test summary not found
14165 04:52:47 WARNING - TEST-UNEXPECTED-FAIL | dom/media/webrtc/tests/mochitests/test_enumerateDevices_getUserMediaFake.html | application timed out after 370 seconds with no output
14171 04:53:02 WARNING - PROCESS-CRASH | dom/media/webrtc/tests/mochitests/test_enumerateDevices_getUserMediaFake.html | application crashed [@ __epoll_pwait]
19994 04:53:03 ERROR - No tests run or test summary not found
20115 04:59:56 WARNING - TEST-UNEXPECTED-FAIL | dom/media/webrtc/tests/mochitests/test_groupId.html | application timed out after 370 seconds with no output
20121 05:00:25 WARNING - PROCESS-CRASH | dom/media/webrtc/tests/mochitests/test_groupId.html | application crashed [@ __epoll_pwait]
25892 05:00:27 ERROR - No tests run or test summary not found
26013 05:07:21 WARNING - TEST-UNEXPECTED-FAIL | dom/media/webrtc/tests/mochitests/test_enumerateDevices.html | application timed out after 370 seconds with no output
26019 05:07:36 WARNING - PROCESS-CRASH | dom/media/webrtc/tests/mochitests/test_enumerateDevices.html | application crashed [@ __epoll_pwait]
31866 05:07:37 ERROR - No tests run or test summary not found
|
Reporter | |
Updated•1 year ago
|
|
||
Updated•1 year ago
|
|
||
Comment 1•1 year ago
•
|
||
test_enumerateDevices_legacy.html got as far as "Device label is empty", the last subtest before the getUserMedia() call.
The other tests all perform a getUserMedia() call before any of their own subtests (apart from the "Reason cannot be empty" from requestFlakyTimeout()) and none of their subtests are logged.
They fail on the first attempt to run.
Apparently the getUserMedia() call is not completing.
The tests run successfully on test-android-em-7.0-x86_64-qr/debug-geckoview-test-verify-nofis, so the failures appear specific to isolated-process.
|
|
||
Comment 2•1 year ago
•
|
||
Why are isolated-process test-verify jobs tier 2 when non-verify isolated-process jobs are tier 3?
|
|
||
Comment 3•1 year ago
|
||
Guessing tier 3 came from https://phabricator.services.mozilla.com/D115390
|
|
Reporter | |
Comment 4•1 year ago
|
||
Update: in the end, bug 1528042 landed without D179146, the known-bad TV andoid mochitests were never turned off in the end. Happy to close this unless we feel there's value in leaving it open?
|
|
Reporter | |
Updated•1 year ago
|
|
|
||
Comment 5•1 year ago
|
||
Hard to say whether there's much value in turning off individual tests given any test with gUM is going to timeout.
Turning off all test-verify isolated-process tests involving gUM might be helpful, but failures may not be limited to gUM so maybe all test-verify isolated-process mochitests should be tier 3, like the non-verify ones.
I've grown accustomed to ignoring certain TV failures (e.g. timeouts on Mac), but I do get needinfo?ed often on them, so they do waste time.
So I don't have a strong opinion. I'd lean towards tier 3, in which case this bug may not be so helpful.
Description
•