fast/peerconnection/RTCRtpSender-setParameters-crash.html failing on chromium.win/Win7 Tests (dbg)(1) |
||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of toyoshim@google.com ...... too many results, data snipped.... and 40 other(s) in webkit_layout_tests failing on chromium.win/Win7 Tests (dbg)(1) Builders failed on: - Win7 Tests (dbg)(1): https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29
,
Apr 18 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/81f17cb2241ab29dc07cc55f83e715ce2606fa0a commit 81f17cb2241ab29dc07cc55f83e715ce2606fa0a Author: Takashi Toyoshima <toyoshim@chromium.org> Date: Wed Apr 18 07:26:37 2018 Update LayoutTests/TestExpectations Suppress fast/peerconnection/RTCRtpSender-setParameters-crash.html timeout for Windows. Bug: 834177 Change-Id: I7fc2b96ca0329da34cbdd4f969ffc34b0a85142e Tbr: orphis@chromium.org Notry: true Reviewed-on: https://chromium-review.googlesource.com/1016225 Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#551604} [modify] https://crrev.com/81f17cb2241ab29dc07cc55f83e715ce2606fa0a/third_party/WebKit/LayoutTests/TestExpectations
,
Apr 18 2018
,
Apr 18 2018
Thanks for handling this. The test was expected to crash triggering a DCHECK in WebRTC, I wonder why it did timeout this time instead. The test will be moved with the other non crashing ones when the underlying WebRTC library is fixed. |
||
►
Sign in to add a comment |
||
Comment 1 by toyoshim@chromium.org
, Apr 18 2018Owner: orphis@chromium.org
Status: Assigned (was: Available)