-
- Notifications
You must be signed in to change notification settings - Fork 33.8k
http2: emit timeout on compat request and response #22252
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.
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
Conversation
2b4cdd8 to e8f319f Compare | Rerun linter: https://ci.nodejs.org/job/node-test-linter/21196/ |
| Please don't add |
mcollina left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
| Landed in 32902d0 ... successful ci runs: #22252 (comment) + https://ci.nodejs.org/job/node-test-linter/21196/ |
| Hi @jasnell -- working on backporting this fix. It seems like in Node 8, the |
Fixes: nodejs#20079 PR-URL: nodejs#22252 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
| @kjin I think this shows some underlining fragility of those tests. I would prefer to increase that timeout to |
| @mcollina Thanks. I'll open a PR to add that to master, and annotate the backported version of this commit in the 8.x backport to increase the timeout as well. |
v8.x Backport Note: The timeout has been increased to 10ms. Fixes: nodejs#20079 PR-URL: nodejs#22252 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Alternative for: #20918
Fixes: #20079
ping @mcollina @apapirovski
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes