RESOLVED FIXED 170701
LayoutTest webrtc/datachannel/bufferedAmountLowThreshold.html is a flaky failure
https://bugs.webkit.org/show_bug.cgi?id=170701
Summary LayoutTest webrtc/datachannel/bufferedAmountLowThreshold.html is a flaky failure
Ryan Haddad
Reported 2017-04-10 15:25:41 PDT
LayoutTest webrtc/datachannel/bufferedAmountLowThreshold.html is a flaky failure https://build.webkit.org/results/Apple%20Sierra%20Debug%20WK2%20(Tests)/r215180%20(401)/results.html https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=webrtc%2Fdatachannel%2FbufferedAmountLowThreshold.html --- /Volumes/Data/slave/sierra-debug-tests-wk2/build/layout-test-results/webrtc/datachannel/bufferedAmountLowThreshold-expected.txt +++ /Volumes/Data/slave/sierra-debug-tests-wk2/build/layout-test-results/webrtc/datachannel/bufferedAmountLowThreshold-actual.txt @@ -1,7 +1,7 @@ CONSOLE MESSAGE: line 76: channel send is throwing CONSOLE MESSAGE: line 76: channel send is throwing -PASS Default buffer threshold +FAIL Default buffer threshold assert_true: got onbufferedamountlow event expected true got false PASS Large buffer threshold reached PASS Medium buffer threshold not reached
Attachments
Patch (3.07 KB, patch)
2017-04-21 13:50 PDT, youenn fablet
no flags
Patch (6.18 KB, patch)
2017-04-21 14:18 PDT, youenn fablet
no flags
Patch (6.25 KB, patch)
2017-04-21 14:19 PDT, youenn fablet
no flags
Ryan Haddad
Comment 1 2017-04-21 11:50:41 PDT
Marked test as flaky in https://trac.webkit.org/r215622.
youenn fablet
Comment 2 2017-04-21 13:50:08 PDT
youenn fablet
Comment 3 2017-04-21 14:18:47 PDT
youenn fablet
Comment 4 2017-04-21 14:19:41 PDT
youenn fablet
Comment 5 2017-04-26 11:31:55 PDT
ping review
WebKit Commit Bot
Comment 6 2017-04-26 15:04:28 PDT
Comment on attachment 307803 [details] Patch Clearing flags on attachment: 307803 Committed r215833: <http://trac.webkit.org/changeset/215833>
WebKit Commit Bot
Comment 7 2017-04-26 15:04:29 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.