-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
test: Http2Stream server stream session destroy tests in one file #15624
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
server.on( | ||
'stream', | ||
common.mustCall((stream) => { | ||
const errorJSON = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you name this something else since it's not actually JSON?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!
Renamed it to errorObj
c3887df
to
a7609e2
Compare
@trivikr this needs a rebase |
@BridgeAR rebase complete! |
@abouthiroppy The error in CI is the CONFLICT in 3-way merge https://ci.nodejs.org/job/node-test-commit/12680/console This conflict is removal of first line |
a7609e2
to
48e5d2d
Compare
48e5d2d
to
3ffd096
Compare
@abouthiroppy Instead of merge, I performed rebase as explained in the documentation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
The CI failed again. As per the console output, the failure was on linux and aix. The CI documentation states that sometimes "flaky" tests on specific platforms might fail. Is this one of those failures? |
The test failures on AIX and Centos 32-bit x64 Linux were unrelated to this PR, CI can be considered to have passed. |
failure in AIX:
While this does not hint any possibility of being related to this PR, I don't remember seeing this failure earlier, it is not listed as flaky either. @gibfahn - are you familiar with this failure, or do we have a tracker for this? cenOS failure:
No idea about this, but looks to be evidently unrelated. |
@gireeshpunathil AIX failure is #15656 |
PR-URL: #15624 Refs: #14985 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
This doesn't appear to land cleanly on v8.x. Would someone familiar with backport be willing to take a look? |
PR-URL: nodejs/node#15624 Refs: nodejs/node#14985 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
Quick ping re: backport |
v8.x backport PR created at #16072 |
PR-URL: nodejs#15624 Refs: nodejs#14985 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
PR-URL: #15624 Refs: #14985 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
This PR includes all server stream session destroy tests in one file
Refs: #14985
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
test, http2