Closed
Bug 1558480
Opened 5 years ago
Closed 5 years ago
[wpt-sync] Sync PR 17266 - Use `assert_approx_equals` in MediaSource tests
Categories
(Core :: Audio/Video: Playback, defect, P4)
Core
Audio/Video: Playback
Tracking
()
RESOLVED
FIXED
mozilla69
Tracking | Status | |
---|---|---|
firefox69 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
References
()
Details
(Whiteboard: [wptsync upstream])
Sync web-platform-tests PR 17266 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/17266
Details from upstream follow.
Philip Jägenstedt <philip@foolip.org> wrote:
Use
assert_approx_equals
in MediaSource testsThe
threeDecimalPlaces
helper usingnumber.toFixed(3)
allowed for
a maximum difference of 0.001 for a pair like 0.0005 / 0.00149999, but
had no lower limit on the difference, a pair like 0.0004999 / 0.0005
would fail.This may be the cause of a Safari failure
!EQ(6.548, 6.549)
:
https://wpt.fyi/results/media-source/mediasource-endofstream.html?run_id=255090001
Assignee | ||
Updated•5 years ago
|
Component: web-platform-tests → Audio/Video: Playback
Product: Testing → Core
Assignee | ||
Comment 1•5 years ago
|
||
Pushed to try https://treeherder.mozilla.org/#/jobs?repo=try&revision=01e02ed4d9b635a6e5d1334a31bd8aa42ea5ed6a
Assignee | ||
Comment 2•5 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=77028e683c9fdd5b9d9fedb72cfffa26fa333a1f
Assignee | ||
Comment 3•5 years ago
|
||
Failed to get results from try push
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/76fec97619b3 [wpt PR 17266] - Use `assert_approx_equals` in MediaSource tests, a=testonly
Comment 5•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox69:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
Assignee | ||
Updated•5 years ago
|
Whiteboard: [wptsync downstream] → [wptsync upstream]
You need to log in
before you can comment on or make changes to this bug.
Description
•