Closed
Bug 1775942
Opened 3 years ago
Closed 2 years ago
Intermittent browser/base/content/test/webrtc/browser_devices_select_audio_output.js | single tracking bug
Categories
(Core :: WebRTC, defect, P3)
Core
WebRTC
Tracking
()
RESOLVED
DUPLICATE
of bug 1812236
People
(Reporter: jmaher, Unassigned)
References
Details
(Keywords: intermittent-failure, intermittent-testcase)
No description provided.
Reporter | ||
Comment 1•3 years ago
|
||
Additional information about this bug failures and frequency patterns can be found by running: ./mach test-info failure-report --bug 1775942
Updated•3 years ago
|
Severity: -- → S4
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 7•2 years ago
•
|
||
The time to run each test increases by about 12s each time when run "10 times in one browser, in chaos mode".
*** Start BrowserChrome Test Results ***
checking window state
TEST-START | browser/base/content/test/webrtc/browser_devices_select_audio_output.js
GECKO(1480) | TEST DEVICES: No test devices found (in media.{audio,video}_loopback_dev, using fake streams.
GECKO(1480) | 2022-12-13 10:25:40.172 firefox[1480:20303] Persistent UI failed to open file file:///Users/cltbld/Library/Saved%20Application%20State/org.mozilla.nightly.savedState/window_1.data: No such file or directory (2)
GECKO(1480) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
GECKO(1480) | MEMORY STAT | vsize 15986MB | residentFast 287MB | heapAllocated 117MB
TEST-OK | browser/base/content/test/webrtc/browser_devices_select_audio_output.js | took 20493ms
checking window state
TEST-START | browser/base/content/test/webrtc/browser_devices_select_audio_output.js
GECKO(1480) | TEST DEVICES: No test devices found (in media.{audio,video}_loopback_dev, using fake streams.
GECKO(1480) | MEMORY STAT | vsize 7805MB | residentFast 287MB | heapAllocated 116MB
TEST-OK | browser/base/content/test/webrtc/browser_devices_select_audio_output.js | took 30574ms
checking window state
TEST-START | browser/base/content/test/webrtc/browser_devices_select_audio_output.js
GECKO(1480) | TEST DEVICES: No test devices found (in media.{audio,video}_loopback_dev, using fake streams.
GECKO(1480) | MEMORY STAT | vsize 7800MB | residentFast 282MB | heapAllocated 117MB
TEST-OK | browser/base/content/test/webrtc/browser_devices_select_audio_output.js | took 44060ms
checking window state
TEST-START | browser/base/content/test/webrtc/browser_devices_select_audio_output.js
GECKO(1480) | TEST DEVICES: No test devices found (in media.{audio,video}_loopback_dev, using fake streams.
GECKO(1480) | MEMORY STAT | vsize 7801MB | residentFast 283MB | heapAllocated 116MB
TEST-OK | browser/base/content/test/webrtc/browser_devices_select_audio_output.js | took 56407ms
checking window state
TEST-START | browser/base/content/test/webrtc/browser_devices_select_audio_output.js
GECKO(1480) | TEST DEVICES: No test devices found (in media.{audio,video}_loopback_dev, using fake streams.
GECKO(1480) | MEMORY STAT | vsize 7801MB | residentFast 283MB | heapAllocated 116MB
TEST-OK | browser/base/content/test/webrtc/browser_devices_select_audio_output.js | took 69687ms
checking window state
TEST-START | browser/base/content/test/webrtc/browser_devices_select_audio_output.js
GECKO(1480) | TEST DEVICES: No test devices found (in media.{audio,video}_loopback_dev, using fake streams.
GECKO(1480) | MEMORY STAT | vsize 7802MB | residentFast 283MB | heapAllocated 118MB
TEST-OK | browser/base/content/test/webrtc/browser_devices_select_audio_output.js | took 82731ms
Without chaos mode, there is no increase.
Different browser-chrome tests are not showing the same increase in a more recent run.
Updated•2 years ago
|
See Also: → tv-chaosmode-timeout-wpt
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 10•2 years ago
|
||
Assuming this is test-verify/chaosmode specific, let's dupe this to bug 1810922, the general issue here. We likely want to use that bug to land an across-the-board increase to the timeout threshold for mochitests (or maybe just mochitest-browser-chrome, or whatever set of suites are running into this trouble).
You need to log in
before you can comment on or make changes to this bug.
Description
•