Skip to content

test: make flaky test stricter - #33539

Closed
ronag wants to merge 1 commit into
nodejs:masterfrom
nxtedition:fix-stress-flaky
Closed

test: make flaky test stricter#33539
ronag wants to merge 1 commit into
nodejs:masterfrom
nxtedition:fix-stress-flaky

Conversation

@ronag

@ronagronag commented May 24, 2020

Copy link
Copy Markdown
Member

Refs: #4066

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

@nodejs-github-botnodejs-github-bot added the test Issues and PRs related to the tests. label May 24, 2020
@ronag

ronag commented May 24, 2020

Copy link
Copy Markdown
MemberAuthor

@ronagronag added the http Issues or PRs related to the http subsystem. label May 24, 2020
Make assertions in flaky test stricter to possibly
make it easier to determine the root cause.
Refs: nodejs#4066
@ronagronag changed the title test: try to resolve flaky testtest: make flaky test strictMay 25, 2020
@ronag
ronagforce-pushed the fix-stress-flaky branch from 48204cd to 16495c1CompareMay 25, 2020 06:52
@ronag
ronag marked this pull request as ready for review May 25, 2020 06:52
@ronagronag changed the title test: make flaky test stricttest: make flaky test stricterMay 25, 2020
@ronag
ronag requested a review from BridgeARMay 25, 2020 06:52
@ronag

Copy link
Copy Markdown
MemberAuthor

Haven't been able to make the flaky test fail to debug this and it's unclear how it hits the failure. I've made the test a bit stricter hoping that future failures maight provide more information.

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@BridgeAR

Copy link
Copy Markdown
Member

The error that came up was ERR_STREAM_DESTROYED. It is not clear why the stream was destroyed but this might of course help debugging.

@ronag

Copy link
Copy Markdown
MemberAuthor

The error that came up was ERR_STREAM_DESTROYED. It is not clear why the stream was destroyed but this might of course help debugging.

Yes, but that should not happen unless it gets into the "response" state. Which this change ensures it should not.

@BridgeARBridgeAR left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

RSLGTM

@BridgeAR
BridgeAR requested review from lpinca and mcollinaMay 25, 2020 13:42

@mcollinamcollina left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

lgtm

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

Copy link
Copy Markdown
MemberAuthor

Landed in 9949a2e

ronag added a commit that referenced this pull request May 26, 2020
Make assertions in flaky test stricter to possibly
make it easier to determine the root cause.
Refs: #4066
PR-URL: #33539
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
@ronagronag closed this May 26, 2020
codebytere pushed a commit that referenced this pull request Jun 18, 2020
Make assertions in flaky test stricter to possibly
make it easier to determine the root cause.
Refs: #4066
PR-URL: #33539
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
@codebyterecodebytere mentioned this pull request Jun 28, 2020
codebytere pushed a commit that referenced this pull request Jun 30, 2020
Make assertions in flaky test stricter to possibly
make it easier to determine the root cause.
Refs: #4066
PR-URL: #33539
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
codebytere pushed a commit that referenced this pull request Jul 8, 2020
Make assertions in flaky test stricter to possibly
make it easier to determine the root cause.
Refs: #4066
PR-URL: #33539
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
@codebyterecodebytere mentioned this pull request Jul 13, 2020
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.httpIssues or PRs related to the http subsystem.testIssues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

@ronag@nodejs-github-bot@BridgeAR@mcollina@jasnell@lpinca