Bug 151949

Summary: [Streams API] pipeTo tests are failing
Product: WebKit Reporter: Xabier Rodríguez Calvar <calvaris>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: NEW ---    
Severity: Normal CC: lmoura, youennf
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   

Description Xabier Rodríguez Calvar 2015-12-07 11:07:23 PST
We are just flagging these tests as pipeTo specification is not complete. When it becomes more complete, we'll have a deeper look.
Comment 1 Xabier Rodríguez Calvar 2015-12-07 12:28:56 PST
Now it is failing in GTK+ too.
Comment 2 Xabier Rodríguez Calvar 2015-12-07 12:35:32 PST
Committed r193644: <http://trac.webkit.org/changeset/193644>
Comment 3 Lauro Moura 2020-08-26 13:58:39 PDT
After the last round of stream commits, pipe-to.html keeps failing with this diff (from a Catalina build):

-FAIL Piping to a writable stream that does not consume the writes fast enough exerts backpressure on the source |this| is not a Promise
+FAIL Piping to a writable stream that does not consume the writes fast enough exerts backpressure on the source assert_equals: at t = 0 ms, ws should be writable expected (string) "writable" but got (undefined) undefined

The test still expects WritableStream to have the 'state' attribute, but it is some detail from the reference implementation, not part of the public WritableStraem API, right?

Btw, testing with both GTK and WPE removing the state check fails at 225ms with:

-FAIL Piping to a writable stream that does not consume the writes fast enough exerts backpressure on the source |this| is not a Promise
+FAIL Piping to a writable stream that does not consume the writes fast enough exerts backpressure on the source assert_array_equals: at t = 225 ms, the two enqueued chunks in rs did not cause backpressure property 1, expected 1 but got 0