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: fix flaky test-net-socket-timeout-unref #6003

Closed
wants to merge 1 commit into from

Conversation

Trott
Copy link
Member

@Trott Trott commented Apr 1, 2016

Pull Request check-list

Please make sure to review and check all of these items:

  • Does make -j8 test (UNIX) or vcbuild test nosign (Windows) pass with
    this change (including linting)?
  • Is the commit message formatted according to [CONTRIBUTING.md][0]?

Affected core subsystem(s)

test, net

Description of change

Throw immediately on socket timeout rather than checking boolean in exit
handler.

Fixes: #5128

Throw immediately on socket timeout rather than checking boolean in exit
handler.

Fixes: nodejs#5128
@Trott Trott added net Issues and PRs related to the net subsystem. test Issues and PRs related to the tests. lts-watch-v4.x labels Apr 1, 2016
@Trott
Copy link
Member Author

Trott commented Apr 1, 2016

Stress test confirming flakiness of current version on master: https://ci.nodejs.org/job/node-stress-single-test/584/nodes=pi2-raspbian-wheezy/console

Stress test showing this version is not flaky: https://ci.nodejs.org/job/node-stress-single-test/583/nodes=pi2-raspbian-wheezy/console

CI: https://ci.nodejs.org/job/node-test-pull-request/2128/

@Trott
Copy link
Member Author

Trott commented Apr 1, 2016

@nodejs/testing

@santigimeno
Copy link
Member

LGTM

process.on('exit', function() {
assert.strictEqual(timedout, false,
'Socket timeout should not hold loop open');
sockets.push({socket: socket, timeout: T * 1000});
Copy link
Contributor

Choose a reason for hiding this comment

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

should this timout be platform specific?

Copy link
Member Author

Choose a reason for hiding this comment

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

This is a socket timeout and not a timer, so I'm inclined to not make it platform dependent if it doesn't need to be.

Copy link
Contributor

Choose a reason for hiding this comment

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

ahhh... /me leaves and reads more about socket time outs

@MylesBorins
Copy link
Contributor

LGTM with above nit assuming CI is green

Trott added a commit to Trott/io.js that referenced this pull request Apr 4, 2016
Throw immediately on socket timeout rather than checking boolean in exit
handler.

PR-URL: nodejs#6003
Fixes: nodejs#5128
Reviewed-By: Myles Borins <myles.borins@gmail.com>
@Trott
Copy link
Member Author

Trott commented Apr 4, 2016

Landed in c60faf6

@Trott Trott closed this Apr 4, 2016
MylesBorins pushed a commit that referenced this pull request Apr 5, 2016
Throw immediately on socket timeout rather than checking boolean in exit
handler.

PR-URL: #6003
Fixes: #5128
Reviewed-By: Myles Borins <myles.borins@gmail.com>
This was referenced Apr 5, 2016
MylesBorins pushed a commit that referenced this pull request Apr 11, 2016
Throw immediately on socket timeout rather than checking boolean in exit
handler.

PR-URL: #6003
Fixes: #5128
Reviewed-By: Myles Borins <myles.borins@gmail.com>
@MylesBorins MylesBorins mentioned this pull request Apr 11, 2016
@Trott Trott deleted the log-it branch January 13, 2022 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
net Issues and PRs related to the net subsystem. test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants