Skip to content

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

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-botnodejs-github-bot added the test Issues and PRs related to the tests. label Feb 9, 2020
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Comment threadtest/parallel/test-repl-history-navigation.js Outdated
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@BridgeARBridgeAR added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Feb 10, 2020
@addaleax

Copy link
Copy Markdown
Member

Landed in 9da57a8

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: #31708Fixes: #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: #31708Fixes: #31094
Reviewed-By: Denys Otrishko <shishugi@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
@codebyterecodebytere mentioned this pull request Feb 17, 2020
@targos

Copy link
Copy Markdown
Member

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

@targostargos removed author ready PRs that have at least one approval, no pending requests for changes, and a CI started. 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#31708Fixes: 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: #31708Fixes: #31094
Reviewed-By: Denys Otrishko <shishugi@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
@targostargos mentioned this pull request May 2, 2020
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

testIssues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Flaky parallel/test-repl-history-navigation

6 participants

@BridgeAR@nodejs-github-bot@addaleax@targos@jasnell@lundibundi