-
-
Notifications
You must be signed in to change notification settings - Fork 33.5k
Closed
Labels
flaky-testIssues and PRs related to the tests with unstable failures on the CI.Issues and PRs related to the tests with unstable failures on the CI.http2Issues or PRs related to the http2 subsystem.Issues or PRs related to the http2 subsystem.
Description
- Test: test-http2-client-jsstream-destroy
- Platform: OSX
- Console Output:
node:events:306
throw er; // Unhandled 'error' event
^
Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
at new NodeError (node:internal/errors:277:15)
at TLSSocket.Writable.write (node:internal/streams/writable:324:11)
at JSSocket._write (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/parallel/test-http2-client-jsstream-destroy.js:25:17)
at doWrite (node:internal/streams/writable:407:12)
at clearBuffer (node:internal/streams/writable:566:7)
at JSSocket.Writable.uncork (node:internal/streams/writable:347:7)
at JSStreamSocket.doWrite (node:internal/js_stream_socket:176:17)
at JSStream.onwrite (node:internal/js_stream_socket:33:57)
Emitted 'error' event on ClientHttp2Stream instance at:
at emitErrorNT (node:internal/streams/destroy:188:8)
at emitErrorCloseNT (node:internal/streams/destroy:153:3)
at processTicksAndRejections (node:internal/process/task_queues:80:21) {
code: 'ERR_STREAM_DESTROYED'
}
Metadata
Metadata
Assignees
Labels
flaky-testIssues and PRs related to the tests with unstable failures on the CI.Issues and PRs related to the tests with unstable failures on the CI.http2Issues or PRs related to the http2 subsystem.Issues or PRs related to the http2 subsystem.