Skip to content

net: enable autoSelectFamily by default#46790

Merged
Trott merged 1 commit intonodejs:mainfrom
ShogunPanda:autoselectfamily-default-on-effective
Apr 5, 2023
Merged

net: enable autoSelectFamily by default#46790
Trott merged 1 commit intonodejs:mainfrom
ShogunPanda:autoselectfamily-default-on-effective

Conversation

@ShogunPanda
Copy link
Contributor

This PR enables the family auto selection algorithm by default.

It also renames the --enable-network-family-autoselection in favor of --no-network-family-autoselection (the old one is still available as an alias).

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/net

@nodejs-github-bot nodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. needs-ci PRs that need a full CI run. net Issues and PRs related to the net subsystem. labels Feb 23, 2023
@ShogunPanda ShogunPanda added the semver-major PRs that contain breaking changes and should be released in the next major version. label Feb 23, 2023
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

@ShogunPanda ShogunPanda force-pushed the autoselectfamily-default-on-effective branch from ffa07c3 to 07f04b2 Compare February 27, 2023 08:39
@ShogunPanda ShogunPanda added the request-ci Add this label to start a Jenkins CI on a PR. label Feb 27, 2023
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Feb 27, 2023
@nodejs-github-bot

This comment was marked as outdated.

@ShogunPanda
Copy link
Contributor Author

@nodejs/tsc I need another TSC approval for this to land. Can you please help me?

@ShogunPanda ShogunPanda added commit-queue Add this label to land a pull request using GitHub Actions. commit-queue-squash Add this label to instruct the Commit Queue to squash all the PR commits into the first one. labels Mar 3, 2023
@nodejs-github-bot nodejs-github-bot added commit-queue-failed An error occurred while landing this pull request using GitHub Actions. and removed commit-queue Add this label to land a pull request using GitHub Actions. labels Mar 3, 2023
@nodejs-github-bot
Copy link
Collaborator

Commit Queue failed
- Loading data for nodejs/node/pull/46790
✔  Done loading data for nodejs/node/pull/46790
----------------------------------- PR info ------------------------------------
Title      net: enable autoSelectFamily by default (#46790)
Author     Paolo Insogna  (@ShogunPanda)
Branch     ShogunPanda:autoselectfamily-default-on-effective -> nodejs:main
Labels     c++, net, semver-major, needs-ci, commit-queue-squash
Commits    3
 - net: enable autoSelectFamily by default
 - net: linted code
 - doc: apply suggestions from PR review
Committers 2
 - Paolo Insogna 
 - GitHub 
PR-URL: https://github.com/nodejs/node/pull/46790
Reviewed-By: Matteo Collina 
Reviewed-By: Robert Nagy 
Reviewed-By: James M Snell 
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/46790
Reviewed-By: Matteo Collina 
Reviewed-By: Robert Nagy 
Reviewed-By: James M Snell 
--------------------------------------------------------------------------------
   ⚠  Commits were pushed since the last review:
   ⚠  - doc: apply suggestions from PR review
   ℹ  This PR was created on Thu, 23 Feb 2023 09:58:50 GMT
   ✔  Approvals: 3
   ✔  - Matteo Collina (@mcollina) (TSC): https://github.com/nodejs/node/pull/46790#pullrequestreview-1311021655
   ✔  - Robert Nagy (@ronag) (TSC): https://github.com/nodejs/node/pull/46790#pullrequestreview-1315324532
   ✔  - James M Snell (@jasnell) (TSC): https://github.com/nodejs/node/pull/46790#pullrequestreview-1320904552
   ✔  Last GitHub CI successful
   ℹ  Last Full PR CI on 2023-02-27T08:46:33Z: https://ci.nodejs.org/job/node-test-pull-request/50051/
   ⚠  Commits were pushed after the last Full PR CI run:
   ⚠  - doc: apply suggestions from PR review
- Querying data for job/node-test-pull-request/50051/
   ✔  Last Jenkins CI successful
--------------------------------------------------------------------------------
   ✔  Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/4326246111

@ShogunPanda ShogunPanda added request-ci Add this label to start a Jenkins CI on a PR. and removed commit-queue-failed An error occurred while landing this pull request using GitHub Actions. labels Mar 3, 2023
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Mar 3, 2023
@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

Copy link
Member

@RafaelGSS RafaelGSS left a comment

Choose a reason for hiding this comment

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

LGTM.

@aduh95 aduh95 requested a review from Trott April 5, 2023 14:12
@Trott
Copy link
Member

Trott commented Apr 5, 2023

@nodejs/tsc @nodejs/net I chose the default connection timeout of 250ms by following the Happy Eyeballs spec. Do you think I should increase it (for instance, in the CI in order to get a green we need 2.5s)?

My inclination would be to split the tests up into multiple files and/or move them to sequential. (The test I flagged for this only failed if it was run with a lot of other tests--or itself--simultaneously. I couldn't get it to fail running in isolation.)

@Trott
Copy link
Member

Trott commented Apr 5, 2023

The last CI that ran was yellow, but there's still a (strange) failure showing up in the GitHub CI wideget:

image

I'll land this manually.

@ShogunPanda
Copy link
Contributor Author

Sorry, I misexplained.
I was not referring to the CI this time. We can move those tests as sequential in the future as you suggested.
But do you think all these failures can reflect frequent problem for final users if we choose this timeout value?

Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
PR-URL: nodejs#46790
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Robert Nagy <ronagy@icloud.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
@Trott Trott force-pushed the autoselectfamily-default-on-effective branch from e76851c to 8b51c1a Compare April 5, 2023 15:32
@Trott Trott merged commit 8b51c1a into nodejs:main Apr 5, 2023
@ShogunPanda
Copy link
Contributor Author

The last CI that ran was yellow, but there's still a (strange) failure showing up in the GitHub CI wideget:

image

I'll land this manually.

Looking at the logs, it seems a machine is out of disk space.

Anyway, I'll wait for you to land this. Thanks!

@Trott
Copy link
Member

Trott commented Apr 5, 2023

Landed in 8b51c1a

@Trott
Copy link
Member

Trott commented Apr 5, 2023

Thanks for all the hard work and patience on this!

@Trott
Copy link
Member

Trott commented Apr 5, 2023

Oh, gosh, it looks like maybe we didn't run CITGM.... 😬

@ShogunPanda
Copy link
Contributor Author

My pleasure.❤️
I'll never give up after the CI! 😁

@ShogunPanda
Copy link
Contributor Author

Oh, gosh, it looks like maybe we didn't run CITGM.... 😬

Lol.
Ok, let me know if there are failures and I'll address them immediately.

@Trott
Copy link
Member

Trott commented Apr 5, 2023

Oh, gosh, it looks like maybe we didn't run CITGM.... 😬

Not a big deal--we should definitely do it before landing, but we'll just do it now and if things blow up there, we'll know we have to be cautious about releasing it....

@ShogunPanda
Copy link
Contributor Author

Sounds good. I'll try to promptly address any problem.

@Trott
Copy link
Member

Trott commented Apr 5, 2023

CITGM on the current main branch, now that this PR just landed: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/3144/

For comparison, here's the most recent CITGM that wasn't for 16.x: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/3141/ which was for #47182

@Trott
Copy link
Member

Trott commented Apr 5, 2023

Could definitely use a look from some more versed-in-CITGM folks (@nodejs/citgm, @nodejs/releasers) but I don't think there are any significant new problems with the CITGM results. The only one I noticed that seemed like maybe it's something to investigate is prom-client failing to install in about half of the runs. That didn't happen in the "control" run but I'm not really seeing how the issue is this change.

https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/3144/nodes=osx1015/testReport/junit/(root)/citgm/prom_client_v14_2_0/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c++ Issues and PRs that require attention from people who are familiar with C++. needs-ci PRs that need a full CI run. net Issues and PRs related to the net subsystem. semver-major PRs that contain breaking changes and should be released in the next major version.

Projects

None yet

Development

Successfully merging this pull request may close these issues.