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

http2: add test for head request is not finished #24308

Closed
wants to merge 1 commit into from

Conversation

ronag
Copy link
Member

@ronag ronag commented Nov 11, 2018

Adds test for #24283. Not actually fixed. Just test.

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

@nodejs-github-bot nodejs-github-bot added the test Issues and PRs related to the tests. label Nov 11, 2018
@ronag ronag force-pushed the fix-head-finished branch 3 times, most recently from 8cb5560 to 75d254a Compare November 11, 2018 17:10
@ronag ronag changed the title http2: fix head request is finished http2: add test for head request is not finished Nov 11, 2018
@addaleax addaleax added the wip Issues and PRs that are still a work in progress. label Nov 12, 2018
@addaleax
Copy link
Member

@ronag I’ve added the WIP label, feel free to ask for it to be removed if that’s not accurate. If you have a hard time fixing this, you can also consider moving this test to test/known_issues/, where we keep tests that we expect to fail (but want to have pass at some point in the future).

@ronag
Copy link
Member Author

ronag commented Nov 12, 2018

@addaleax: Moved to known_issues. Ready for merge?

@addaleax addaleax added the http2 Issues or PRs related to the http2 subsystem. label Nov 12, 2018
@addaleax
Copy link
Member

@ronag This would still need to be reviewed – I didn’t take an in-depth look yet (i.e. I don’t know if the current behaviour might be okay, or how hard it would be to fix this).

/cc @nodejs/http2

.listen(0, common.mustCall(function() {
const port = server.address().port;
server.once('request', common.mustCall((req, res) => {
assert.ok(!res.finished);
Copy link
Member

Choose a reason for hiding this comment

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

This is the assertion that fails? Can you please add a comment?

@ronag
Copy link
Member Author

ronag commented Nov 13, 2018

@mcollina Comments added

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

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

LGTM. I would prefer that this included a fix, but that's ok too.

@ronag
Copy link
Member Author

ronag commented Nov 13, 2018

Sorry, I tried... it's a bit over my head unfortunately


const common = require('../common');
if (!common.hasCrypto)
common.skip('missing crypto');
Copy link
Member Author

Choose a reason for hiding this comment

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

@mcollina For future reference, what is the purpose of this? I just followed the other tests, not sure if or why it would be needed?

Copy link
Member

Choose a reason for hiding this comment

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

@ronag The http2 module requires encryption, so if Node.js was compiled without crypto, then http2 tests need to be skipped.

@ronag
Copy link
Member Author

ronag commented Nov 13, 2018

Close in favour of #24339?

@ronag ronag closed this Jul 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
http2 Issues or PRs related to the http2 subsystem. test Issues and PRs related to the tests. wip Issues and PRs that are still a work in progress.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants