web-platform-tests / web-platform-tests/wpt
wptserve H2 tests flakily failing
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 6.2k
- Forks
- 3.9k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 586
Description
I've seen this a few times recently; see e.g. this Azure Pipelines step. (Logs attached here for archival reasons: 209.txt.)
That job had:
FAILED wptserve/tests/functional/test_response.py::TestH2Response::test_raw_data_frame
FAILED wptserve/tests/functional/test_server.py::TestFileHandlerH2::test_not_handled
FAILED wptserve/tests/functional/test_server.py::TestRewriterH2::test_rewrite
FAILED wptserve/tests/functional/test_server.py::TestRequestHandlerH2::test_exception
They all failed with:
httpx.ReadTimeout: The read operation timed out
And had captured logs like:
----------------------------- Captured log setup ------------------------------
INFO root:server.py:867 Starting http2 server on https://localhost:51070/
---------------------------- Captured log teardown ----------------------------
ERROR root:server.py:426 (923a45a7) Closing Connection -
[WinError 10054] An existing connection was forcibly closed by the remote host
INFO root:server.py:885 Stopped http server on localhost:51070
Pretty sure I've also seen this on not-Windows too.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the four failing tests in wptserve/tests/functional/test_response.py and wptserve/tests/functional/test_server.py, then review the linked Azure Pipelines logs and 209.txt. Reproduce the HTTP/2 timeout and compare the captured setup and teardown logs. Done means the tests no longer fail intermittently on the affected platforms.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100