| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Does this allow a bug during flakiness? |
Sorry, something went wrong.
Didn't get you? 😅😅 |
Sorry, something went wrong.
Sorry, something went wrong.
Co-authored-by: Matteo Collina <matteo.collina@gmail.com>
Sorry, something went wrong.
There was a problem hiding this comment.
lgtm
Sorry, something went wrong.
Refs: nodejs/reliability#508 Refs: #46333 PR-URL: #46855 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Refs: nodejs/reliability#508 Refs: #46333 PR-URL: #46855 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Refs: nodejs/reliability#508 Refs: #46333 PR-URL: #46855 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
| Back | FazBrowse Home | New Git URL |
The test test-http-remove-header-stays-removed.js seems to be slightly flaky as seen in nodejs/reliability#508 and also reproducible locally by running python3 tools/test.py test/parallel/test-http-remove-header-stays-removed.js --repeat 1000
Since the test checks that the socket is closed right after receiving the last chunk of data hence moved the checking for the same after the data has been received and slightly increased the timeout, the flakiness no longer reproduces
Refs: nodejs/reliability#508
Refs: #46333