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

flaky: parallel/test-https-foafssl #24397

Closed
refack opened this issue Nov 16, 2018 · 7 comments
Closed

flaky: parallel/test-https-foafssl #24397

refack opened this issue Nov 16, 2018 · 7 comments
Labels
flaky-test Issues and PRs related to the tests with unstable failures on the CI. https Issues or PRs related to the https subsystem. openssl Issues and PRs related to the OpenSSL dependency. test Issues and PRs related to the tests. windows Issues and PRs related to the Windows platform.

Comments

@refack
Copy link
Contributor

refack commented Nov 16, 2018

  • Version: master
  • Platform: Windows 10
  • Subsystem: openssl

/CC @nodejs/platform-windows @nodejs/crypto

@refack refack added https Issues or PRs related to the https subsystem. test Issues and PRs related to the tests. openssl Issues and PRs related to the OpenSSL dependency. flaky-test Issues and PRs related to the tests with unstable failures on the CI. windows Issues and PRs related to the Windows platform. labels Nov 16, 2018
@refack
Copy link
Contributor Author

refack commented Nov 16, 2018

/CC @nodejs/http

@Trott
Copy link
Member

Trott commented Nov 21, 2018

Can't reproduce locally. Let's try CI stress test:

https://ci.nodejs.org/job/node-stress-single-test/2093/

RUN_TEST: -J --repeat 10 parallel/test-https-foafssl
RUN_TIMES: 100
RUN_LABEL: win10-1p-vs2015 and win10-vs2017

Both hosts are Azure hosts in that stress test run, just like in the only reported failure above.

@refack
Copy link
Contributor Author

refack commented Nov 21, 2018

@Trott
Copy link
Member

Trott commented Nov 23, 2018

Relevant stress tests are green.
¯\(ツ)

@Trott
Copy link
Member

Trott commented Aug 2, 2020

It's back.

https://ci.nodejs.org/job/node-test-binary-windows-js-suites/5131/RUN_SUBSET=2,nodes=win10-COMPILED_BY-vs2019/console

test-azure_msft-win10_vcbt2015-x64-4

00:19:56 not ok 743 parallel/test-https-foafssl
00:19:56   ---
00:19:56   duration_ms: 120.185
00:19:56   severity: fail
00:19:56   exitcode: 1
00:19:56   stack: |-
00:19:56     timeout
00:19:56     got request
00:19:56   ...

@Trott Trott reopened this Aug 2, 2020
Trott added a commit to Trott/io.js that referenced this issue Aug 2, 2020
The test is timing out once in a very long while on Windows CI. It is
unclear where the test gets stuck, so add more debugging statements to
try to locate it.

Refs: nodejs#24397
@Trott
Copy link
Member

Trott commented Aug 2, 2020

CI stress test showing the failure on test-azure_msft-win10_vs2019-x64-2: https://ci.nodejs.org/job/node-stress-single-test/156/nodes=win10-vs2019/console

Trott added a commit to Trott/io.js that referenced this issue Aug 2, 2020
The test is timing out once in a very long while on Windows CI. It is
unclear where the test gets stuck, so add more debugging statements to
try to locate it.

Refs: nodejs#24397
jasnell pushed a commit that referenced this issue Aug 7, 2020
The test is timing out once in a very long while on Windows CI. It is
unclear where the test gets stuck, so add more debugging statements to
try to locate it.

Refs: #24397

PR-URL: #34603
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: James M Snell <[email protected]>
jasnell pushed a commit that referenced this issue Aug 7, 2020
The test is timing out once in a very long while on Windows CI. It is
unclear where the test gets stuck, so add more debugging statements to
try to locate it.

Refs: #24397

PR-URL: #34603
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: James M Snell <[email protected]>
addaleax pushed a commit that referenced this issue Aug 8, 2020
The test is timing out once in a very long while on Windows CI. It is
unclear where the test gets stuck, so add more debugging statements to
try to locate it.

Refs: #24397

PR-URL: #34603
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: James M Snell <[email protected]>
addaleax pushed a commit that referenced this issue Aug 8, 2020
The test is timing out once in a very long while on Windows CI. It is
unclear where the test gets stuck, so add more debugging statements to
try to locate it.

Refs: #24397

PR-URL: #34603
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: James M Snell <[email protected]>
codebytere pushed a commit that referenced this issue Aug 11, 2020
The test is timing out once in a very long while on Windows CI. It is
unclear where the test gets stuck, so add more debugging statements to
try to locate it.

Refs: #24397

PR-URL: #34603
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: James M Snell <[email protected]>
codebytere pushed a commit that referenced this issue Aug 11, 2020
The test is timing out once in a very long while on Windows CI. It is
unclear where the test gets stuck, so add more debugging statements to
try to locate it.

Refs: #24397

PR-URL: #34603
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: James M Snell <[email protected]>
addaleax pushed a commit that referenced this issue Sep 22, 2020
The test is timing out once in a very long while on Windows CI. It is
unclear where the test gets stuck, so add more debugging statements to
try to locate it.

Refs: #24397

PR-URL: #34603
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: James M Snell <[email protected]>
addaleax pushed a commit that referenced this issue Sep 22, 2020
The test is timing out once in a very long while on Windows CI. It is
unclear where the test gets stuck, so add more debugging statements to
try to locate it.

Refs: #24397

PR-URL: #34603
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: James M Snell <[email protected]>
addaleax pushed a commit that referenced this issue Sep 22, 2020
The test is timing out once in a very long while on Windows CI. It is
unclear where the test gets stuck, so add more debugging statements to
try to locate it.

Refs: #24397

PR-URL: #34603
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: James M Snell <[email protected]>
addaleax pushed a commit that referenced this issue Sep 22, 2020
The test is timing out once in a very long while on Windows CI. It is
unclear where the test gets stuck, so add more debugging statements to
try to locate it.

Refs: #24397

PR-URL: #34603
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: James M Snell <[email protected]>
@targos
Copy link
Member

targos commented Nov 20, 2021

Closing as there was no recent activity

@targos targos closed this as completed Nov 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flaky-test Issues and PRs related to the tests with unstable failures on the CI. https Issues or PRs related to the https subsystem. openssl Issues and PRs related to the OpenSSL dependency. test Issues and PRs related to the tests. windows Issues and PRs related to the Windows platform.
Projects
None yet
Development

No branches or pull requests

3 participants