Open Bug 1187903 Opened 9 years ago Updated 1 year ago

Intermittent test_eme_playback.html, test_eme_stream_capture_blocked_case2.html, test_eme_stream_capture_blocked_case3.html | Test timed out

Categories

(Core :: Audio/Video: Playback, defect, P3)

x86_64
Linux
defect

Tracking

()

Tracking Status
firefox41 --- unaffected
firefox42 --- disabled
firefox43 --- disabled
firefox-esr38 --- unaffected

People

(Reporter: RyanVM, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: intermittent-failure, regression, Whiteboard: [tests disabled on Windows][leave open])

20:01:19 INFO - 2390 INFO TEST-PASS | dom/media/test/test_eme_stream_capture_blocked_case2.html | [finished 640x360 then 640x480-18_case2_load] Length of array should match number of running tests
20:01:19 INFO - 2391 INFO [19:56:15.930] 640x360 then 640x480-18_case2 loadeddata
20:01:19 INFO - 2392 INFO TEST-PASS | dom/media/test/test_eme_stream_capture_blocked_case2.html | 640x360 then 640x480-18_case2 should reach loadeddata
20:01:19 INFO - 2393 INFO TEST-PASS | dom/media/test/test_eme_stream_capture_blocked_case2.html | Should throw an error creating a MediaElementSource on an EME video.
20:01:19 INFO - 2394 INFO [finished 640x360 then 640x480-18_case2] remaining= 400x300 audio&video tracks, each with its key-4_case2
20:01:19 INFO - 2395 INFO TEST-PASS | dom/media/test/test_eme_stream_capture_blocked_case2.html | [finished 640x360 then 640x480-18_case2] Length of array should match number of running tests
20:01:19 INFO - 2396 INFO [19:56:15.995] 640x480@959kbps with 1st keys then 640x480@624kbps with 2nd keys-11_case2 stalled
20:01:19 INFO - 2397 INFO [19:56:16.201] 640x360 then 640x480-18_case2 progress
20:01:19 INFO - 2398 INFO [19:56:16.463] 640x480@624kbps with 1st keys then 640x480@959kbps with 2nd keys-12_case2 stalled
20:01:19 INFO - 2399 INFO [19:56:17.47] 400x300 with presentation size 533x300-13_case2 stalled
20:01:19 INFO - 2400 INFO [19:56:17.397] 400x300 as-is then 400x300 presented as 533x300-14_case2 stalled
20:01:19 INFO - 2401 INFO [19:56:17.777] 400x225-15_case2 stalled
20:01:19 INFO - 2402 INFO [19:56:18.216] 640x360-16_case2 stalled
20:01:19 INFO - 2403 INFO [19:56:18.619] 400x225 then 640x360-17_case2 stalled
20:01:19 INFO - 2404 INFO [19:56:19.2] 640x360 then 640x480-18_case2 stalled
20:01:19 INFO - 2405 INFO TEST-UNEXPECTED-FAIL | dom/media/test/test_eme_stream_capture_blocked_case2.html | Test timed out.
20:01:19 INFO - reportError@SimpleTest/TestRunner.js:334:7
20:01:19 INFO - TestRunner._checkForHangs@SimpleTest/TestRunner.js:354:7
20:01:19 INFO - 2406 INFO Test timed out. Remaining tests=400x300 audio&video tracks, each with its key-4_case2
20:01:19 INFO - MEMORY STAT | vsize 20973297MB | residentFast 2217MB
20:01:19 INFO - 2407 INFO TEST-OK | dom/media/test/test_eme_stream_capture_blocked_case2.html | took 314047ms
And a leak for good measure.
Component: Audio/Video → Audio/Video: Playback
Summary: Intermittent test_eme_stream_capture_blocked_case2.html | Test timed out → Intermittent test_eme_playback.html,test_eme_stream_capture_blocked_case2.html,test_eme_stream_capture_blocked_case3.html | Test timed out
This is a top EME failure at the moment. Can we please get someone to look at this?
Flags: needinfo?(jyavenard)
Jean-Yves, does this EME test timeout look like an MSE problem or an EME problem?
Blocks: EME
Priority: -- → P2
ni? myself to skip these tests on Win8 on Friday
Flags: needinfo?(ryanvm)
Disabled on Windows debug.

https://hg.mozilla.org/integration/mozilla-inbound/rev/9a39576f3c5a
https://hg.mozilla.org/releases/mozilla-aurora/rev/b46847796e06
Flags: needinfo?(ryanvm)
Flags: needinfo?(jyavenard)
Whiteboard: [tests disabled on Windows][leave open]
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #144)
> Disabled on Windows debug.
> 
> https://hg.mozilla.org/integration/mozilla-inbound/rev/9a39576f3c5a
> https://hg.mozilla.org/releases/mozilla-aurora/rev/b46847796e06

I'd have appreciated it if you ni? me, or a module peer, rather than disabling
our tests and leaving us flying blind without knowing about it.

We have been aggressively uplifting EME fixes to Beta. We could have broken Netflix without knowing about it because you disabled our tests without telling us.
I ni? a module peer in comment 63. I disabled the tests over a week later. How this bug was handled was within policy, especially for one that was as frequent as it was. If you'd like to discuss further privately via email, feel free. But I don't think callouts in the bug nearly a month later is overly productive.
Sorry, Yes, you did follow policy. I didn't see comment 63.

It's grating because I'm the one responsible for these tests and I didn't know about it and I was on PTO at the time this happened. I feel like we need a better system to notify devs when their tests get disabled.
I can't see ni? in comment 63. Is it a special flag visible to the module owner only?
oops! My bad. I saw nothing because I didn't login to bugzilla.
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #153)
> I ni? a module peer in comment 63. I disabled the tests over a week later.
> How this bug was handled was within policy, especially for one that was as
> frequent as it was. If you'd like to discuss further privately via email,
> feel free. But I don't think callouts in the bug nearly a month later is
> overly productive.

However, clearing the need-info as in comment 144 meant this slipped of jya's radar.
Mass change P2 -> P3
Priority: P2 → P3
Summary: Intermittent test_eme_playback.html,test_eme_stream_capture_blocked_case2.html,test_eme_stream_capture_blocked_case3.html | Test timed out → Intermittent test_eme_playback.html, test_eme_stream_capture_blocked_case2.html, test_eme_stream_capture_blocked_case3.html | Test timed out
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.