Closed Bug 1393260 Opened 2 years ago Closed 2 years ago

Intermittent dom/media/test/reftest/street.mp4.seek.html == http://localhost:53633/1503502208044/666/reftest/street.mp4.seek.html | image comparison, max difference: 255, number of differing pixels: 231394

Categories

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

defect

Tracking

()

RESOLVED FIXED
mozilla57
Tracking Status
firefox57 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: bechen)

References

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

Assignee: nobody → bechen
I found that the when the testcase seek to 0.4666667s, the file duration from MDSM is not stable. For example, if the duration is 0.3s when seeking, the seek operation to 0.4666667s will seek to 0.3s.
The duration is unstable when seeking because the street.mp4 is a fragment mp4 file. So the total duration updated at runtime from MediaFormatReader instead metadata.
Comment on attachment 8903441 [details]
Bug 1393260 - Reftest for the 55th frame of gizmo.mp4.

https://reviewboard.mozilla.org/r/175290/#review180300

::: dom/media/test/reftest/gizmo.mp4.seek.html:4
(Diff revision 1)
> +<!DOCTYPE HTML>
> +<html class="reftest-wait">
> +<!--This testing should match the 15th frame of gizmo.mp4. The
> +55th frame's time is 1.8s, so seek to a time which is a little

15th or 55th?

::: dom/media/test/reftest/gizmo.mp4.seek.html:5
(Diff revision 1)
> +<!DOCTYPE HTML>
> +<html class="reftest-wait">
> +<!--This testing should match the 15th frame of gizmo.mp4. The
> +55th frame's time is 1.8s, so seek to a time which is a little
> +greater than 1.8s, the display frame should be the 55th frame.

same here.

::: dom/media/test/reftest/reftest.list:4
(Diff revision 1)
>  skip-if(Android) fuzzy-if(OSX,22,49977) skip-if(winWidget) fuzzy-if(gtkWidget&&layersGPUAccelerated,70,600) HTTP(..) == short.mp4.firstframe.html short.mp4.firstframe-ref.html
>  skip-if(Android) fuzzy-if(OSX,23,51392) fuzzy-if(winWidget,59,76797) fuzzy-if(gtkWidget&&layersGPUAccelerated,60,1800) HTTP(..) == short.mp4.lastframe.html short.mp4.lastframe-ref.html
>  skip-if(Android) skip-if(winWidget) fuzzy-if(gtkWidget&&layersGPUAccelerated,55,4281) fuzzy-if(OSX,3,111852) HTTP(..) == bipbop_300_215kbps.mp4.lastframe.html bipbop_300_215kbps.mp4.lastframe-ref.html
> -skip-if(Android) fuzzy-if(winWidget,65,307093) HTTP(..) == street.mp4.seek.html street.mp4.15thframe-ref.html
> +skip-if(Android) HTTP(..) == gizmo.mp4.seek.html gizmo.mp4.55thframe-ref.html

should we need fuzzy-if(...) here?
Attachment #8903441 - Flags: review?(alwu) → review+
Comment on attachment 8903441 [details]
Bug 1393260 - Reftest for the 55th frame of gizmo.mp4.

https://reviewboard.mozilla.org/r/175290/#review180300

> should we need fuzzy-if(...) here?

We need to wait for the try server result then fill the fuzzy value.
Keywords: checkin-needed
Pushed by ryanvm@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/7bc57009bd4d
Reftest for the 55th frame of gizmo.mp4. r=alwu
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/7bc57009bd4d
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla57
You need to log in before you can comment on or make changes to this bug.