Open Bug 1839502 Opened 1 year ago Updated 1 year ago

test_streams_element_capture.html "current time at end" failures with multiple media files

Categories

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

defect

Tracking

()

People

(Reporter: karlt, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

I've seen various similar failures with different media files. The particular files with failures seem to depend on the platform with some failures being reasonably consistent. The "Got" numbers can vary.

Got 0.255419, expected at least 0.266; redirect.sjs?domain=mochi.test:8888&file=320x240.ogv-39 current time at end
Got 2.28, expected at least 2.3; audio-overhang.ogg-36 current time at end
Got 1.021678, expected at least 1.06; bipbop_audio_aac_8k.mp4-80 current time at end
Got 1.027482, expected at least 1.06; bipbop_audio_aac_22.05k.mp4-81 current time at end
Got 1.039092, expected at least 1.06; bipbop_audio_aac_44.1k.mp4-82 current time at end
Got 1.033287, expected at least 1.06; bipbop_audio_aac_48k.mp4-83 current time at end
Got 1.041995, expected at least 1.06; bipbop_audio_aac_88.2k.mp4-84 current time at end
Got 1.050702, expected at least 1.06; bipbop_audio_aac_96k.mp4-85 current time at end
Got 0.992, expected at least 1.011; bipbop_short_pixel_metadata_smaller_than_in_stream_vp8.webm-46 current time at end
Got 4.136054, expected at least 4.138; bug482461-theora.ogv-14 current time at end
Got 1.950476, expected at least 1.958; bug500311.ogv-15 current time at end
Got 4.205333, expected at least 4.208; bug516323.ogv-18 current time at end
Got 2.893786, expected at least 2.903; bug556821.ogv-19 current time at end
Got 0.264126, expected at least 0.266; chain.ogv-29 current time at end
Got 1.08, expected at least 1.081; short-video.ogv-16 current time at end
Got 1.959183, expected at least 1.967; split.webm-41 current time at end
Got 1.008, expected at least 1.019; vbr-head.mp3-70 current time at end
Got 0.997333, expected at least 1; vp9cake-short.webm-0 current time at end

The failures rate has become much higher since the test was disabled for bug 1554808 but there already existed a similar intermittent failure tracked in bug 1557149.

You need to log in before you can comment on or make changes to this bug.