Closed Bug 1782844 Opened 3 years ago Closed 3 years ago

Intermittent TEST-UNEXPECTED-TIMEOUT | dom/media/webrtc/tests/mochitests/test_getUserMedia_gumWithinGum.html | application timed out after 370 seconds with no output

Categories

(Core :: WebRTC: Audio/Video, defect, P5)

Product:
Core
Component:
WebRTC: Audio/Video
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1784717

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure)

Filed by: mlaza [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=386205212&repo=mozilla-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/fV3JDfE2QA6EowdCJRI8HA/runs/0/artifacts/public/logs/live_backing.log

[task 2022-08-03T00:14:54.674Z] 00:14:54     INFO - TEST-PASS | dom/media/webrtc/tests/mochitests/test_getUserMedia_gumWithinGum.html | Current src should still be an empty string 
[task 2022-08-03T00:14:54.675Z] 00:14:54     INFO - Start loopback tone at 440
[task 2022-08-03T00:14:54.676Z] 00:14:54     INFO - Call getUserMedia for {"audio":{"autoGainControl":false,"echoCancellation":false,"noiseSuppression":false}}
[task 2022-08-03T00:14:54.676Z] 00:14:54     INFO - Buffered messages finished
[task 2022-08-03T00:14:54.677Z] 00:14:54    ERROR - TEST-UNEXPECTED-TIMEOUT | dom/media/webrtc/tests/mochitests/test_getUserMedia_gumWithinGum.html | application timed out after 370 seconds with no output
[task 2022-08-03T00:14:54.678Z] 00:14:54    ERROR - Force-terminating active process(es).
[task 2022-08-03T00:14:54.679Z] 00:14:54     INFO - Determining child pids from psutil...
[task 2022-08-03T00:14:54.680Z] 00:14:54     INFO - [8963, 9007, 9108, 9113, 9160, 9205, 9208, 9325, 9330]
[task 2022-08-03T00:14:54.682Z] 00:14:54     INFO - ==> process 8927 launched child process 8947
[task 2022-08-03T00:14:54.683Z] 00:14:54     INFO - ==> process 8927 launched child process 8963
[task 2022-08-03T00:14:54.685Z] 00:14:54     INFO - ==> process 8927 launched child process 9007
[task 2022-08-03T00:14:54.686Z] 00:14:54     INFO - ==> process 8927 launched child process 9029
[task 2022-08-03T00:14:54.687Z] 00:14:54     INFO - ==> process 8927 launched child process 9108
[task 2022-08-03T00:14:54.688Z] 00:14:54     INFO - ==> process 8927 launched child process 9113
[task 2022-08-03T00:14:54.690Z] 00:14:54     INFO - ==> process 8927 launched child process 9160
[task 2022-08-03T00:14:54.691Z] 00:14:54     INFO - ==> process 8927 launched child process 9205
[task 2022-08-03T00:14:54.693Z] 00:14:54     INFO - ==> process 8927 launched child process 9208
[task 2022-08-03T00:14:54.694Z] 00:14:54     INFO - ==> process 8927 launched child process 9325
[task 2022-08-03T00:14:54.695Z] 00:14:54     INFO - ==> process 8927 launched child process 9330
[task 2022-08-03T00:14:54.696Z] 00:14:54     INFO - Found child pids: {8963, 9029, 9160, 9325, 9007, 9330, 8947, 9108, 9205, 9208, 9113}
[task 2022-08-03T00:14:54.697Z] 00:14:54     INFO - Failed to get child procs
[task 2022-08-03T00:14:54.699Z] 00:14:54     INFO - Killing process: 8963
[task 2022-08-03T00:14:54.700Z] 00:14:54     INFO - TEST-INFO | started process screentopng
[task 2022-08-03T00:14:54.835Z] 00:14:54     INFO - TEST-INFO | screentopng: exit 0
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.