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

[v18.x backport] test: assume priv ports start at 1024 if it can't be changed #46537

Closed

Conversation

KrayzeeKev
Copy link
Contributor

An update to test/parallel/test-cluster-bind-privileged-port.js checks the lowest privileged port to ensure 42 is privileged This only works on kernels > 4.1. On older kernels, this is locked at 1024 so the check is not needed.

Fixes: #45838

An update to test/parallel/test-cluster-bind-privileged-port.js
checks the lowest privileged port to ensure 42 is privileged
This only works on kernels > 4.1. On older kernels, this is
locked at 1024 so the check is not needed.

Fixes: nodejs#45838
@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. test Issues and PRs related to the tests. v18.x Issues that can be reproduced on v18.x or PRs targeting the v18.x-staging branch. labels Feb 7, 2023
@danielleadams
Copy link
Contributor

@KrayzeeKev do you still want to land this? There are merge conflicts that need to be resolved.

@KrayzeeKev
Copy link
Contributor Author

I'd love to see it landed either via this PR or the discussion on slack mentioned it would happen "automatically" based on the v19 patch. Since v18 is with us for a while (and we'll run it here until 20 hits LTS) and it breaks tests for RHEL-7 and anything based on it (which is us, for now), I'd really like to see it in the code. Surprised there are conflicts since nothing else has changed in that code. Unless the v19/main patch has already been applied - that'll explain why this "manual" one might cause issues.

@KrayzeeKev KrayzeeKev closed this Apr 13, 2023
@KrayzeeKev
Copy link
Contributor Author

This appears to have been backported based on the v19 commit. This entire branch/PR is not required

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-ci PRs that need a full CI run. test Issues and PRs related to the tests. v18.x Issues that can be reproduced on v18.x or PRs targeting the v18.x-staging branch.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants