-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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: fix flaky test-net-GH-5504 #9461
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.
LGTM but it sure raises the question of why removing the watchdog timer would fix the flakiness.
Could it be that if the timer fires and the server and/or client processes are still alive, killing them doesn't cause the process to exit immediately so the |
Just a note that I think a |
The test is failing on `SmartOS` quite often. Removing the timeout seems to fix it. Fixes: nodejs#8930 PR-URL: nodejs#9461 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
4b43343
to
f8f67d2
Compare
The test is failing on `SmartOS` quite often. Removing the timeout seems to fix it. Fixes: #8930 PR-URL: #9461 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
The test is failing on `SmartOS` quite often. Removing the timeout seems to fix it. Fixes: #8930 PR-URL: #9461 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
Checklist
make -j8 test
(UNIX), orvcbuild test nosign
(Windows) passesAffected core subsystem(s)
Description of change
The test is failing on
SmartOS
quite often. Removing the timeout seemsto fix it.
It's an alternate fix to #9444