-
Notifications
You must be signed in to change notification settings - Fork 29.1k
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
Investigate flaky test-http2-server-rst-stream #16688
Labels
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
http2
Issues or PRs related to the http2 subsystem.
test
Issues and PRs related to the tests.
windows
Issues and PRs related to the Windows platform.
Comments
Trott
added
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
http2
Issues or PRs related to the http2 subsystem.
test
Issues and PRs related to the tests.
windows
Issues and PRs related to the Windows platform.
labels
Nov 2, 2017
Yeah, I think this test just makes too many assumptions about the flow. I've had it on my list for a while. I believe it also fails on node-chakracore and they marked it as flaky. Will work on it shortly so assigning to myself. |
3 tasks
3 tasks
I believe I saw this failing locally as well. |
cjihrig
pushed a commit
to cjihrig/node
that referenced
this issue
Nov 6, 2017
PR-URL: nodejs#16690 Fixes: nodejs#16688 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
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.
http2
Issues or PRs related to the http2 subsystem.
test
Issues and PRs related to the tests.
windows
Issues and PRs related to the Windows platform.
https://ci.nodejs.org/job/node-test-binary-windows/12447/COMPILED_BY=vs2015,RUNNER=win2008r2-vs2017,RUN_SUBSET=1/console:
@nodejs/http2 @nodejs/testing @nodejs/platform-windows @nodejs/build
The text was updated successfully, but these errors were encountered: