Intermittent TEST-UNEXPECTED-TIMEOUT | /mediacapture-streams/GUM-unknownkey-option-param.https.html | expected OK



3 years ago
3 years ago


(Reporter: intermittent-bug-filer, Unassigned)



Firefox Tracking Flags

(Not tracked)


(Whiteboard: [needinfo jib 8/3/16])

Any idea what might be going on here? I don't see any useful output in the log.
backlog: --- → webrtc/webaudio+
Rank: 32
Component: Audio/Video → WebRTC: Audio/Video
Flags: needinfo?(jib)
Priority: -- → P3
Whiteboard: [needinfo jib 8/3/16]
Ok, I remember now, lots of these webplatform tests are allowed to fail, but still exercise the code, so please excuse my catching up.

The only thing I can think of is that with bug 1213517 landed, we're handling concurrent constraints for gUM differently, and a lot of these tests (the ones that succeed anyway) fire off gUM calls without ever stopping the resulting streams, meaning they're effectively concurrent requests (which they probably shouldn't be since having tests depend on tests that ran before and garbage collection is usually a bad idea, so they should probably be re-written, which we should file an issue on with the spec people).

So it's possible a combination of these tests end up altering the settings of the camera when it is already running, which we previously disallowed, but now this ends up restarting the camera, which is new code, and that could be where it hangs, possibly.

Gcp, does this sound plausible?

Flags: needinfo?(gpascutto)
See Also: → 1289665
Or it could totally be related to the 100+ other TEST-UNEXPECTED-TIMEOUT bugs filed just since Monday...
backlog: webrtc/webaudio+ → ---
Component: WebRTC: Audio/Video → web-platform-tests
Product: Core → Testing
I've only written the Android tests, so I have no idea if what you describe is correct for the others or not.
Flags: needinfo?(gpascutto)
Tracked in bug 1291234; will likely never happen again in this test.
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.