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

test: fix flaky parallel/test-repl-history-navigation test by BridgeAR · Pull Request #31708 · nodejs/node · GitHub

/ node Public

test: fix flaky parallel/test-repl-history-navigation test - #31708

Closed
BridgeAR wants to merge 2 commits into
nodejs:masterfrom
BridgeAR:2020-02-09-fix-repl-history-navigation-test
Closed

test: fix flaky parallel/test-repl-history-navigation test#31708
BridgeAR wants to merge 2 commits into
nodejs:masterfrom
BridgeAR:2020-02-09-fix-repl-history-navigation-test

Conversation

BridgeAR commented Feb 9, 2020

Copy link
Copy Markdown
Member

Two scenarios should be tested:

  1. The completion is triggered and the result is printed before the
    next invocation.
  2. The completion is triggered multiple times right after each other
    without waiting for the result. In that case only the last result
    should be printed.

The first scenario did not need a timeout while the latter did not
need a timeout for the second invocation.

Fixes: #31094

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

Two scenarios should be tested:

1. The completion is triggered and the result is printed before the
   next invocation.
2. The completion is triggered multiple times right after each other
   without waiting for the result. In that case only the last result
   should be printed.

The first scenario did not need a timeout while the latter did not
need a timeout for the second invocation.
nodejs-github-bot added the test Issues and PRs related to Node.js core tests and test infrastructure. label Feb 9, 2020

Copy link
Copy Markdown
Collaborator

Copy link
Copy Markdown
Collaborator

BridgeAR added the author ready PRs with CI started, the required approvals, and no outstanding review comments. label Feb 10, 2020

Copy link
Copy Markdown
Member

Landed in 9da57a8

addaleax closed this Feb 13, 2020
addaleax pushed a commit that referenced this pull request Feb 13, 2020
Two scenarios should be tested:

1. The completion is triggered and the result is printed before the
   next invocation.
2. The completion is triggered multiple times right after each other
   without waiting for the result. In that case only the last result
   should be printed.

The first scenario did not need a timeout while the latter did not
need a timeout for the second invocation.

PR-URL: #31708
Fixes: #31094
Reviewed-By: Denys Otrishko <shishugi@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
codebytere pushed a commit that referenced this pull request Feb 17, 2020
Two scenarios should be tested:

1. The completion is triggered and the result is printed before the
   next invocation.
2. The completion is triggered multiple times right after each other
   without waiting for the result. In that case only the last result
   should be printed.

The first scenario did not need a timeout while the latter did not
need a timeout for the second invocation.

PR-URL: #31708
Fixes: #31094
Reviewed-By: Denys Otrishko <shishugi@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
codebytere mentioned this pull request Feb 17, 2020

targos commented Apr 18, 2020

Copy link
Copy Markdown
Member

depends on semver-minor changes to land on v12.x

targos removed author ready PRs with CI started, the required approvals, and no outstanding review comments. backport-blocked-v12.x labels Apr 25, 2020
targos pushed a commit to targos/node that referenced this pull request Apr 25, 2020
Two scenarios should be tested:

1. The completion is triggered and the result is printed before the
   next invocation.
2. The completion is triggered multiple times right after each other
   without waiting for the result. In that case only the last result
   should be printed.

The first scenario did not need a timeout while the latter did not
need a timeout for the second invocation.

PR-URL: nodejs#31708
Fixes: nodejs#31094
Reviewed-By: Denys Otrishko <shishugi@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
targos pushed a commit that referenced this pull request Apr 28, 2020
Two scenarios should be tested:

1. The completion is triggered and the result is printed before the
   next invocation.
2. The completion is triggered multiple times right after each other
   without waiting for the result. In that case only the last result
   should be printed.

The first scenario did not need a timeout while the latter did not
need a timeout for the second invocation.

PR-URL: #31708
Fixes: #31094
Reviewed-By: Denys Otrishko <shishugi@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.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 Node.js core tests and test infrastructure.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Flaky parallel/test-repl-history-navigation

6 participants


Back | FazBrowse Home | New Git URL