FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

test: fix flaky test-http2-settings-flood by Trott · Pull Request #19349 · nodejs/node · GitHub

/ node Public

test: fix flaky test-http2-settings-flood - #19349

Closed
Trott wants to merge 1 commit into
nodejs:masterfrom
Trott:unflake
Closed

test: fix flaky test-http2-settings-flood#19349
Trott wants to merge 1 commit into
nodejs:masterfrom
Trott:unflake

Conversation

Trott commented Mar 14, 2018

Copy link
Copy Markdown
Member

The test is unreliable on some Windows platforms in its current form.
Make it more robust by using setInterval() to repeat the flooding
until an error is triggered.

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

Trott added the wip Issues and PRs that are still a work in progress. label Mar 14, 2018
nodejs-github-bot added the test Issues and PRs related to the tests. label Mar 14, 2018

Trott commented Mar 14, 2018

Copy link
Copy Markdown
Member Author

Marking as in progress until I can determine that this actually fixes the issue....

Trott commented Mar 14, 2018

Copy link
Copy Markdown
Member Author

Trott force-pushed the unflake branch 2 times, most recently from d35d667 to 38db513 Compare March 14, 2018 21:26

Trott commented Mar 14, 2018

Copy link
Copy Markdown
Member Author

The change "worked" in that the test kept trying but it got ECONNRESET before the flood error. Trying again but swallowing ECONNRESET errors. Really, though, thing to do is probably make the flooding threshold configurable (if it is not) and then reduce it to something really low for this test...

Trott commented Mar 14, 2018

Copy link
Copy Markdown
Member Author

CI: https://ci.nodejs.org/job/node-test-commit/16923/

Well, in that case, it just times out....

Trott commented Mar 14, 2018

Copy link
Copy Markdown
Member Author

One option is to skip the test if ECONNRESET is received, but that may be even worse than the current situation, which unfortunately is that if the test fails, we shrug it off because the test is inherently unreliable.

Trott commented Mar 15, 2018

Copy link
Copy Markdown
Member Author

OMG, doing it in 10K chunks appears to have fixed the problem on Windows! Removing in progress.

CI: https://ci.nodejs.org/job/node-test-pull-request/13689/ (Failure on LinuxONE appears build related and unrelated to this change. Re-run: https://ci.nodejs.org/job/node-test-commit-linuxone/13659/ )

Trott removed the wip Issues and PRs that are still a work in progress. label Mar 15, 2018
The test is unreliable on some Windows platforms in its current form.
Make it more robust by using `setInterval()` to repeat the flooding
until an error is triggered.

Fixes: nodejs#18251

Trott commented Mar 15, 2018

Copy link
Copy Markdown
Member Author

Trott added the author ready PRs that have at least one approval, no outstanding review comments, and a CI started. label Mar 15, 2018

apapirovski left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Nicely done!

Trott commented Mar 16, 2018

Copy link
Copy Markdown
Member Author

Landed in 879f521

Trott closed this Mar 16, 2018
Trott added a commit to Trott/io.js that referenced this pull request Mar 16, 2018
The test is unreliable on some Windows platforms in its current form.
Make it more robust by using `setInterval()` to repeat the flooding
until an error is triggered.

Fixes: nodejs#18251

PR-URL: nodejs#19349
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
targos pushed a commit that referenced this pull request Mar 17, 2018
The test is unreliable on some Windows platforms in its current form.
Make it more robust by using `setInterval()` to repeat the flooding
until an error is triggered.

Fixes: #18251

PR-URL: #19349
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
targos mentioned this pull request Mar 18, 2018
MylesBorins pushed a commit that referenced this pull request Mar 20, 2018
The test is unreliable on some Windows platforms in its current form.
Make it more robust by using `setInterval()` to repeat the flooding
until an error is triggered.

Fixes: #18251

PR-URL: #19349
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
MylesBorins pushed a commit that referenced this pull request Mar 20, 2018
The test is unreliable on some Windows platforms in its current form.
Make it more robust by using `setInterval()` to repeat the flooding
until an error is triggered.

Fixes: #18251

PR-URL: #19349
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
tniessen removed the author ready PRs that have at least one approval, no outstanding review comments, and a CI started. label Mar 24, 2018
codebytere pushed a commit that referenced this pull request Oct 18, 2018
The test is unreliable on some Windows platforms in its current form.
Make it more robust by using `setInterval()` to repeat the flooding
until an error is triggered.

Fixes: #18251

PR-URL: #19349
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

test Issues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants


Back | FazBrowse Home | New Git URL