Skip to content
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

test: replace HTTPPARSER by new resource names #27372

Closed
wants to merge 1 commit into from
Closed

test: replace HTTPPARSER by new resource names #27372

wants to merge 1 commit into from

Conversation

Flarna
Copy link
Member

@Flarna Flarna commented Apr 23, 2019

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

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • commit message follows commit guidelines

@nodejs-github-bot nodejs-github-bot added async_hooks Issues and PRs related to the async hooks subsystem. test Issues and PRs related to the tests. labels Apr 23, 2019
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
@nodejs-github-bot
Copy link
Collaborator

Copy link
Member

@Trott Trott left a 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

@@ -16,7 +16,7 @@ const createdIds = [];
const destroyedIds = [];
async_hooks.createHook({
init: common.mustCallAtLeast((asyncId, type) => {
if (type === 'HTTPPARSER') {
if (type === 'HTTPINCOMINGMESSAGE' || type === 'HTTPCLIENTREQUEST') {
Copy link
Member

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.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Honestly speaking I haven't looked into this in that detail; my focus was to repair the test and to add an assert to avoid such side effect again.
#26961 is still reproducible after #25094 was merged so there is for sure something left in this but this needs more thoughts.

Copy link
Member Author

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.

@Flarna
Copy link
Member Author

Flarna commented Apr 24, 2019

I think the CI fails on freebsd are unrelated.

@Flarna Flarna closed this Apr 24, 2019
@Flarna Flarna reopened this Apr 24, 2019
@Flarna
Copy link
Member Author

Flarna commented Apr 29, 2019

superseded by #27477

@Flarna Flarna closed this Apr 29, 2019
@Flarna Flarna deleted the rename_httpparser branch April 29, 2019 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
async_hooks Issues and PRs related to the async hooks subsystem. test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants