LayoutTest streams/pipe-to.html is a flaky failure https://build.webkit.org/results/Apple%20Sierra%20Debug%20WK2%20(Tests)/r209787%20(1363)/results.html https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=streams%2Fpipe-to.html --- /Volumes/Data/slave/sierra-debug-tests-wk2/build/layout-test-results/streams/pipe-to-expected.txt +++ /Volumes/Data/slave/sierra-debug-tests-wk2/build/layout-test-results/streams/pipe-to-actual.txt @@ -1,3 +1,3 @@ -PASS Piping to a writable stream that does not consume the writes fast enough exerts backpressure on the source +FAIL Piping to a writable stream that does not consume the writes fast enough exerts backpressure on the source assert_equals: at t = 125 ms, ws should be waiting expected "waiting" but got "writable"
This is not a recent regression. This test seems to fail most frequently on macOS debug bots.
Marked test as flaky on macOS debug in http://trac.webkit.org/projects/webkit/changeset/209837
I'm now seeing this test flake on release builds, but with different output: --- /Volumes/Data/slave/sierra-release-tests-wk2/build/layout-test-results/streams/pipe-to-expected.txt +++ /Volumes/Data/slave/sierra-release-tests-wk2/build/layout-test-results/streams/pipe-to-actual.txt @@ -1,3 +1,3 @@ -PASS Piping to a writable stream that does not consume the writes fast enough exerts backpressure on the source +FAIL Piping to a writable stream that does not consume the writes fast enough exerts backpressure on the source assert_array_equals: at t = 475 ms, ws.write should have been called with two chunks lengths differ, expected 2 got 1 https://build.webkit.org/results/Apple%20Sierra%20Release%20WK2%20(Tests)/r212663%20(3734)/results.html Removed debug-only flag from flaky expectation in https://trac.webkit.org/changeset/212670