RTCDTMFSender-ontonechange.https.html is failing |
|||
Issue descriptione.g. https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win7%20Tests%20%28dbg%29%281%29/71778 (but appears across multiple bots going back some time) New failures: FAIL insertDTMF() with default duration and intertoneGap should fire tonechange events at the expected time assert_approx_equals: Expect tonechange event for "2" to be fired approximately after 170 milliseconds expected 170 +/- 400 but got 794 FAIL insertDTMF() with explicit duration and intertoneGap should fire tonechange events at the expected time assert_approx_equals: Expect tonechange event for "B" to be fired approximately after 170 milliseconds expected 170 +/- 400 but got 780 FAIL Calling insertDTMF() multiple times in the middle of tonechange events should cause future tonechanges to be updated the last provided tones assert_equals: Expect current event.tone to be 3 expected "3" but got "1" Since I can't get the flakiness dashboard to show me when this started (but it wasn't in the last couple days), going to disable and leave to WebRTC folk to triage further.
,
Sep 25
hta@: Can you take a look?
,
Sep 25
Will do. This is likely a test that used to fail at a previous step, but is now failing because of the timeout. We need to rewire the logic so that a timeout is not part of the test suite.
,
Oct 3
Fix was landed as an update to https://crbug.com/816475 |
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Sep 24