Bug 1415283 - Increase timeout for tone events in RTCDTMFSender-helper.js; r=jgraham

With the current value of 150 milliseconds we get intermittent timeouts on our
test infrastructure. We are missing by only a small amount, e.g. 6 milliseconds
in Bug 1415283, but it seems safer to increase the timeout to 250 milliseconds so
that we don't end up revisiting this problem in the future.

This also fixes the error message to say milliseconds rather than seconds.

MozReview-Commit-ID: CqjTKZn33q8

--HG--
extra : rebase_source : e5a024c25f24743c764cd43c1e47310f71fcd48a
This commit is contained in:
Dan Minor 2017-11-08 07:10:03 -05:00
Родитель 854ac85615
Коммит 87078513c0
1 изменённых файлов: 2 добавлений и 2 удалений

Просмотреть файл

@ -76,8 +76,8 @@ function test_tone_change_events(testFunc, toneChanges, desc) {
const now = Date.now();
const duration = now - lastEventTime;
assert_approx_equals(duration, expectedDuration, 150,
`Expect tonechange event for "${tone}" to be fired approximately after ${expectedDuration} seconds`);
assert_approx_equals(duration, expectedDuration, 250,
`Expect tonechange event for "${tone}" to be fired approximately after ${expectedDuration} milliseconds`);
lastEventTime = now;