8000 WritableStream: fix TIMEOUT of response-stream-with-broken-then.any.worker · Issue #35421 · servo/servo · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

WritableStream: fix TIMEOUT of response-stream-with-broken-then.any.worker #35421

Open
gterzian opened this issue Feb 11, 2025 · 0 comments
Open

WritableStream: fix TIMEOUT of response-stream-with-broken-then.any.worker #35421

gterzian opened this issue Feb 11, 2025 · 0 comments
Labels
C-untriaged New issues that haven't been triaged yet
8494

Comments

@gterzian
Copy link
Member

Follow-up to #34844

The suite of the following tests is now TIMEOUT for workers only:

servo/tests/wpt/tests/fetch/api/response/response-stream-with-broken-then.any.js

Line 4 in cb588ba

promise_test(async () => {

The last test indeed uses a WritableStream:

servo/tests/wpt/tests/fetch/api/response/response-stream-with-broken-then.any.js

Line 116 in cb588ba

}, 'intercepting arraybuffer to body readable stream conversion via ' +

It's not clear to me what causes the timeout, especially not since it's only for the worker event-loop.

I've tried commenting out the below line:

servo/tests/wpt/tests/fetch/api/response/response-stream-with-broken-then.any.js

Line 113 in cb588ba

await resp.body.pipeTo(ws);

and this indeed removes the timeout.

Note that pipeTo is not implemented yet, so there is a unhandled rejection with a type erro of pipeTo is not a function. But this is the same in a window event-loop, so I don't understand what causes a timeout for workers.
@gterzian gterzian added the C-untriaged New issues that haven't been triaged yet label Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-untriaged New issues that haven't been triaged yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gterzian
0