Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

test: fix flaky test-https-server-close- tests #43216

Merged

Conversation

santigimeno
Copy link
Member

Don't initiate the second connection until the first has been
established.

Refs: nodejs/reliability#289

@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. test Issues and PRs related to the tests. labels May 26, 2022
@santigimeno santigimeno force-pushed the santi/fix_test_https_close_idle branch from f3f6774 to 9f2d594 Compare May 26, 2022 18:31
@lpinca lpinca added the request-ci Add this label to start a Jenkins CI on a PR. label May 28, 2022
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label May 28, 2022
@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

client1Closed = true;
}));
client1.on('connect', common.mustCall(() => {
assert.strictEqual(connections, 1);
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
assert.strictEqual(connections, 1);

It seems that the 'connect' event can be emitted before the 'connection' event on the server. I think we can remove this as the second connection is initiated from the listener of this event anyway.

Copy link
Member

@lpinca lpinca Jun 17, 2022

Choose a reason for hiding this comment

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

@santigimeno are you ok with this? I would like to see if CI is happy after this small change.

Copy link
Member Author

Choose a reason for hiding this comment

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

@lpinca sure thing. Just rebased and pushed with that change. Sorry for the delay. Thanks!

Don't initiate the second connection until the first has been
established.

Refs: nodejs/reliability#289
@santigimeno santigimeno force-pushed the santi/fix_test_https_close_idle branch from 9f2d594 to c0c4661 Compare June 17, 2022 13:11
@lpinca lpinca added the request-ci Add this label to start a Jenkins CI on a PR. label Jun 17, 2022
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jun 17, 2022
@nodejs-github-bot
Copy link
Collaborator

@santigimeno santigimeno added the request-ci Add this label to start a Jenkins CI on a PR. label Jun 17, 2022
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jun 17, 2022
@nodejs-github-bot
Copy link
Collaborator

@F3n67u
Copy link
Member

F3n67u commented Jun 18, 2022

@santigimeno test-http-server-close-idle is also flaky. I filed a issue at #43466. Could this pr fix test-http-server-close-idle flaky and close #43466?

@santigimeno santigimeno changed the title test: fix flaky test-https-server-close-idle test: fix flaky test-https-server-close- tests Jun 18, 2022
@santigimeno
Copy link
Member Author

@santigimeno test-http-server-close-idle is also flaky. I filed a issue at #43466. Could this pr fix test-http-server-close-idle flaky and close #43466?

Yes, this PR fixes 4 very similar flaky tests included the one you mention. The PR title is confusing, I'll change it.

@F3n67u
Copy link
Member

F3n67u commented Jun 18, 2022

@santigimeno test-http-server-close-idle is also flaky. I filed a issue at #43466. Could this pr fix test-http-server-close-idle flaky and close #43466?

Yes, this PR fixes 4 very similar flaky tests included the one you mention. The PR title is confusing, I'll change it.

Great work!

@F3n67u F3n67u added the request-ci Add this label to start a Jenkins CI on a PR. label Jun 18, 2022
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jun 18, 2022
@nodejs-github-bot
Copy link
Collaborator

@F3n67u F3n67u added the flaky-test Issues and PRs related to the tests with unstable failures on the CI. label Jun 18, 2022
@F3n67u
Copy link
Member

F3n67u commented Jun 19, 2022

Could we land this pr now? Those flaky tests often fail on my pr.

@F3n67u F3n67u added the request-ci Add this label to start a Jenkins CI on a PR. label Jun 19, 2022
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jun 19, 2022
@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@lpinca lpinca added the commit-queue Add this label to land a pull request using GitHub Actions. label Jun 19, 2022
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Jun 19, 2022
@nodejs-github-bot nodejs-github-bot merged commit f8f2772 into nodejs:main Jun 19, 2022
@nodejs-github-bot
Copy link
Collaborator

Landed in f8f2772

targos pushed a commit that referenced this pull request Jul 12, 2022
Don't initiate the second connection until the first has been
established.

Refs: nodejs/reliability#289

PR-URL: #43216
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
flaky-test Issues and PRs related to the tests with unstable failures on the CI. needs-ci PRs that need a full CI run. test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants