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: revise test-http-client-default-headers-exist #32493

Merged
merged 1 commit into from
Mar 27, 2020

Conversation

Trott
Copy link
Member

@Trott Trott commented Mar 25, 2020

  • Remove assert.strictEqual where assert.ok suffices
  • Replace countdown with Promise.all()
Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

@nodejs-github-bot nodejs-github-bot added the test Issues and PRs related to the tests. label Mar 25, 2020
@nodejs-github-bot

This comment has been minimized.

@nodejs-github-bot

This comment has been minimized.

}, expectedMethods.length));

server.listen(0, common.mustCall(() => {
expectedMethods.forEach((method) => {
http.request({
Promise.all(expectedMethods.map(async (method) => {
Copy link
Member

Choose a reason for hiding this comment

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

It's not an issue with this particular test, but keep in mind that changing all of these to use Promises is changing the timing of these tests... rather than executing the countdown cleanup logic synchronously it is being deferred to the microtask queue. That could end up causing the test to miss issues that may exist when closing things down synchronously so worth watching... also, keep this issue in mind also when refactoring these :-) .. as I said, not an issue on this particular test but there are some where it may be relevant.

Copy link
Member Author

@Trott Trott Mar 26, 2020

Choose a reason for hiding this comment

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

I want to make sure I understand your point about the cleanup code and the microtask queue. Are you saying that with countdown, the callback that checks things executes synchronously whenever the pertinent .dec() call happens, whereas with Promise.all(), it is whenever the microtask queue runs the resolve callback in the .then() call, so it might execute at a different time and with things in a different state than countdown?

If so: That's something I hadn't considered and worth watching out for. Thanks for pointing it out! (And thanks for making me take a few minutes to re-learn about the microtask queue, which is something I almost never think about!)

@Trott Trott added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Mar 27, 2020
@nodejs-github-bot

This comment has been minimized.

@nodejs-github-bot

This comment has been minimized.

@nodejs-github-bot
Copy link
Collaborator

nodejs-github-bot commented Mar 27, 2020

CI: https://ci.nodejs.org/job/node-test-pull-request/30132/ (:yellow_heart:)

* Remove assert.strictEqual where assert.ok suffices
* Replace countdown with Promise.all()

PR-URL: nodejs#32493
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
@Trott Trott merged commit 436c71d into nodejs:master Mar 27, 2020
@Trott
Copy link
Member Author

Trott commented Mar 27, 2020

Landed in 436c71d

@Trott Trott deleted the def-headers branch March 28, 2020 00:00
addaleax pushed a commit that referenced this pull request Mar 30, 2020
* Remove assert.strictEqual where assert.ok suffices
* Replace countdown with Promise.all()

PR-URL: #32493
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
targos pushed a commit that referenced this pull request Apr 22, 2020
* Remove assert.strictEqual where assert.ok suffices
* Replace countdown with Promise.all()

PR-URL: #32493
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants