- Version: 6.11.4.0
- Platform: Windows server 2012 and 2016
- Subsystem: test
Haven't seen this in CI, but I see it on our Windows boxes all the time.
not ok 550 parallel/test-http-pipeline-flood
---
duration_ms: 0.718
severity: fail
stack: |-
assert.js:80
throw new assert.AssertionError({
^
AssertionError: Unexpected data received
at fail (c:\build\jenkins-new\v6tstwin\x64node\node\test\common\index.js:477:10)
at Socket.mustNotCall (c:\build\jenkins-new\v6tstwin\x64node\node\test\common\index.js:483:5)
at emitOne (events.js:101:20)
at Socket.emit (events.js:188:7)
at readableAddChunk (_stream_readable.js:176:18)
at Socket.Readable.push (_stream_readable.js:134:10)
at TCP.onread (net.js:547:20)
...Example log from when it fails:
backloggedReqs: 1238
res: ServerResponse {
domain: null,
_events: { finish: [Function: resOnFinish] },
_eventsCount: 1,
_maxListeners: undefined,
output: [],
outputEncodings: [],
outputCallbacks: [],
outputSize: 0,
writable: true,
_last: false,
upgrading: false,
chunkedEncoding: false,
shouldKeepAlive: true,
useChunkedEncodingByDefault: true,
sendDate: true,
_removedHeader: { ‘content-length’: false },
_contentLength: null,
_hasBody: true,
_trailer: ‘’,
finished: true,
_headerSent: true,
socket: null,
connection: null,
_header: ‘HTTP/1.1 200 OK\r\ncontent-length: 10240\r\nDate: Wed, 18 Oct 2017 16:03:38 GMT\r\nConnection: keep-alive\r\n\r\n’,
_headers: { ‘content-length’: 10240 },
_headerNames: { ‘content-length’: ‘content-length’ },
_onPendingData: [Function: updateOutgoingData],
statusMessage: ‘OK’,
statusCode: 200 }
Haven't seen this in CI, but I see it on our Windows boxes all the time.
Example log from when it fails: