Skip to content

test: fix test/parallel/test-tls-server-verify.js on Windows CI - #18382

Closed
Trott wants to merge 1 commit into
nodejs:masterfrom
Trott:fix-broken-windows-test
Closed

test: fix test/parallel/test-tls-server-verify.js on Windows CI#18382
Trott wants to merge 1 commit into
nodejs:masterfrom
Trott:fix-broken-windows-test

Conversation

@Trott

@TrottTrott commented Jan 25, 2018

Copy link
Copy Markdown
Member

The test runs two test cases at a time. This is not relevant to what the
test is actually testing. Not sure why doing it that way causes a
deadlock on some Windows servers, but running one at a time fixes it.

Fixes: #18269

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines
Affected core subsystem(s)

test

@TrottTrott added the wip Issues and PRs that are still a work in progress. label Jan 25, 2018
@nodejs-github-botnodejs-github-bot added the test Issues and PRs related to the tests. label Jan 25, 2018
@Trott
Trottforce-pushed the fix-broken-windows-test branch from a2b91a2 to f80676dCompareJanuary 25, 2018 22:52
The test runs two test cases at a time. This is not relevant to what the
test is actually testing. Not sure why doing it that way causes a
deadlock on some Windows servers, but running one at a time fixes it.
Fixes: nodejs#18269
@Trott
Trottforce-pushed the fix-broken-windows-test branch from 54c392f to e3a4fd1CompareJanuary 26, 2018 00:27
@TrottTrott changed the title wip: experiment to fix test-tls-server-verify.js test: fix test/parallel/test-tls-server-verify.js on Windows CIJan 26, 2018
@Trott

Copy link
Copy Markdown
MemberAuthor

@TrottTrott added fast-track PRs that do not need to wait for 48 hours to land. and removed wip Issues and PRs that are still a work in progress. labels Jan 26, 2018
@Trott

Copy link
Copy Markdown
MemberAuthor

No longer in progress. Ready to land, I hope. PTAL. @nodejs/testing

@Trott

Copy link
Copy Markdown
MemberAuthor

Sweet sweet passing test where it was failing before:

ok 411 parallel/test-tls-server-verify --- duration_ms: 10.681

Fast track anyone?

@joyeecheung

Copy link
Copy Markdown
Member

See #1461 and #1836

cc @nodejs/crypto

Should be safe to run them in parallel:

commit 975e5956f06692259a0584e1e31d81d011e20320
Author: João Reis <reis@janeasystems.com>
Date: Fri May 22 14:28:11 2015 +0100
test: run tls-server-verify servers in parallel
Different servers must use different ports. Since we can count only on
common.PORT and common.PORT+1, run only 2 servers in parallel.
Fixes: https://github.com/nodejs/io.js/issues/1461
PR-URL: https://github.com/nodejs/io.js/pull/1836
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>

@apapirovski

Copy link
Copy Markdown
Contributor

I'm happy this is getting fixed but it only started failing reasonably recently and seems like it could be hiding a legitimate bug. The thing is, the real issue in this test might not even be tls but with child_process given its extensive usage.

Maybe a TODO could be left to investigate why the test is failing on Windows when two parallel runTest are executed?

@Trott

Copy link
Copy Markdown
MemberAuthor

investigate why the test is failing on Windows when two parallel runTest are executed?

On it. Hoping to have a known_issues test to submit in a different PR.

@Trott

Copy link
Copy Markdown
MemberAuthor

Landed in 1ecd2be

@TrottTrott closed this Jan 26, 2018
Trott added a commit that referenced this pull request Jan 26, 2018
The test runs two test cases at a time. This is not relevant to what the
test is actually testing. Not sure why doing it that way causes a
deadlock on some Windows servers, but running one at a time fixes it.
Fixes: #18269
PR-URL: #18382
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@evanlucasevanlucas mentioned this pull request Jan 30, 2018
evanlucas pushed a commit that referenced this pull request Jan 30, 2018
The test runs two test cases at a time. This is not relevant to what the
test is actually testing. Not sure why doing it that way causes a
deadlock on some Windows servers, but running one at a time fixes it.
Fixes: #18269
PR-URL: #18382
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
MylesBorins pushed a commit that referenced this pull request Feb 5, 2018
The test runs two test cases at a time. This is not relevant to what the
test is actually testing. Not sure why doing it that way causes a
deadlock on some Windows servers, but running one at a time fixes it.
Fixes: #18269
PR-URL: #18382
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@MylesBorinsMylesBorins mentioned this pull request Feb 7, 2018
MylesBorins pushed a commit that referenced this pull request Feb 7, 2018
The test runs two test cases at a time. This is not relevant to what the
test is actually testing. Not sure why doing it that way causes a
deadlock on some Windows servers, but running one at a time fixes it.
Fixes: #18269
PR-URL: #18382
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
MylesBorins pushed a commit that referenced this pull request Feb 11, 2018
The test runs two test cases at a time. This is not relevant to what the
test is actually testing. Not sure why doing it that way causes a
deadlock on some Windows servers, but running one at a time fixes it.
Fixes: #18269
PR-URL: #18382
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
MylesBorins pushed a commit that referenced this pull request Feb 12, 2018
The test runs two test cases at a time. This is not relevant to what the
test is actually testing. Not sure why doing it that way causes a
deadlock on some Windows servers, but running one at a time fixes it.
Fixes: #18269
PR-URL: #18382
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
MylesBorins pushed a commit that referenced this pull request Feb 13, 2018
The test runs two test cases at a time. This is not relevant to what the
test is actually testing. Not sure why doing it that way causes a
deadlock on some Windows servers, but running one at a time fixes it.
Fixes: #18269
PR-URL: #18382
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
MayaLekova pushed a commit to MayaLekova/node that referenced this pull request May 8, 2018
The test runs two test cases at a time. This is not relevant to what the
test is actually testing. Not sure why doing it that way causes a
deadlock on some Windows servers, but running one at a time fixes it.
Fixes: nodejs#18269
PR-URL: nodejs#18382
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@Trott
Trott deleted the fix-broken-windows-test branch January 13, 2022 22:48
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fast-trackPRs that do not need to wait for 48 hours to land.testIssues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

investigate flaky parallel/test-tls-server-verify on Windows

6 participants

@Trott@joyeecheung@apapirovski@jasnell@cjihrig@nodejs-github-bot