-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Removes FIXME #8689
Removes FIXME #8689
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please don't change file permissions.
I feel like the comment is pointing to an underlying bug in the dgram impl if it should not be necessary. Looks like it's been there since the test was introduced in ALJCepeda@defa637 |
My apologies! The mode change was not intentional, I've reverted back to 644 and ran @Fishrock123 Yes that makes sense. I will investigate |
It's necessary to close the socket otherwise the test will hang
It's necessary to close the socket otherwise the test will hang
When the first And start listening for messages by calling I think this is why you have to
However this seems unusual to me. The other tests will work when I call Thoughts? |
/cc @bnoordhuis I suppose... |
c133999
to
83c7a88
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is fine. Once you start sending data, the socket becomes bound and needs to be closed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM and sorry for the delay, I must've missed the notification.
Can you reword the commit log to something like 'test: remove obsolete comment from dgram test'? Thanks.
Should be completely unnecessary, but CI: https://ci.nodejs.org/job/node-test-pull-request/6314/ |
Landed in 89f8ef2. Thanks! |
Refs: #4640 PR-URL: #8689 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
Refs: nodejs#4640 PR-URL: nodejs#8689 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
Refs: nodejs#4640 PR-URL: nodejs#8689 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
Refs: nodejs#4640 PR-URL: nodejs#8689 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
Refs: #4640 PR-URL: #8689 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
Refs: #4640 PR-URL: #8689 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
Checklist
make -j4 test
(UNIX), orvcbuild test nosign
(Windows) passesAffected core subsystem(s)
Description of change
It's necessary to close the socket otherwise the test will hang
REF #4640