-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
test: replace HTTPPARSER by new resource names #27372
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
The async resource `HTTPPARSER` has been replaced by `HTTPINCOMINGMESSAGE` and `HTTPCLIENTREQUEST` but some tests have not been adapted. As test test-graph.http.js has not failed even it asserted on ´HTTPPARSER` I improved `verify-graph` and adapted the asserts in test-graph.tls-write which failed because of the stricter check. Refs: #25094
Trott
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 if CI passes
| async_hooks.createHook({ | ||
| init: common.mustCallAtLeast((asyncId, type) => { | ||
| if (type === 'HTTPPARSER') { | ||
| if (type === 'HTTPINCOMINGMESSAGE' || type === 'HTTPCLIENTREQUEST') { |
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.
Does HTTPCLIENTREQUEST ever actually happen here? My messing around with this for another PR has that never showing up.
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.
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.
Just tried and it seems HTTPCLIENTREQUEST is never emitted. This is for sure a bug.
|
I think the CI fails on freebsd are unrelated. |
|
superseded by #27477 |
The async resource
HTTPPARSERhas been replaced byHTTPINCOMINGMESSAGEandHTTPCLIENTREQUESTbut some tests havenot been adapted.
As test test-graph.http.js has not failed even it asserted on
HTTPPARSERI improvedverify-graphand adapted the asserts intest-graph.tls-write which failed because of the stricter check.
Refs: #25094
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes