Skip to content

Conversation

@gsnedders
Copy link
Member

Because of the unexpected close, CFNetwork sometimes runs into a retry limit trying to find a working connection. Given we SHOULD be closing gracefully, and these tests are not attempting to test abrupt closure, it makes sense to just change these tests.

The files not changed here are:

tools/wptserve/wptserve/server.py
tools/wptserve/wptserve/handlers.py
tools/wptserve/wptserve/response.py
fetch/h1-parsing/resources/status-code.py
fetch/h1-parsing/resources/message.py

See also #38091.

Because of the unexpected close, CFNetwork sometimes runs into a retry
limit trying to find a working connection. Given we SHOULD be closing
gracefully, and these tests are not attempting to test abrupt closure,
it makes sense to just change these tests.

The files not changed here are:

tools/wptserve/wptserve/server.py
tools/wptserve/wptserve/handlers.py
tools/wptserve/wptserve/response.py
fetch/h1-parsing/resources/status-code.py
fetch/h1-parsing/resources/message.py

See also web-platform-tests#38091.
@annevk
Copy link
Member

annevk commented Feb 14, 2023

@abinpaul1 Chrome seems flaky on the Resource Timing Content-Type tests you added recently. Could you take a look?

@foolip foolip merged commit a8d60f5 into web-platform-tests:master Feb 14, 2023
@foolip
Copy link
Member

foolip commented Feb 14, 2023

Admin merged by request from @gsnedders

@abinpaul1
Copy link
Contributor

@annevk I think it's tracked here : https://bugs.chromium.org/p/chromium/issues/detail?id=1399870 and is being looked at.

@gsnedders gsnedders deleted the close_connection_connection_close branch February 15, 2023 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants