Investigate flaky parallel/test-http-dns-error.js
- Version: v10.x
- Platform: Windows
- Subsystem: test
On test-azure_msft-win2016-x64-4 with VS2017, parallel/test-http-dns-error.js fails with:
19:37:06 not ok 207 parallel/test-http-dns-error
19:37:06 ---
19:37:06 duration_ms: 0.202
19:37:06 severity: fail
19:37:06 exitcode: 1
19:37:06 stack: |-
19:37:06 assert.js:85
19:37:06 throw new AssertionError(obj);
19:37:06 ^
19:37:06
19:37:06 AssertionError [ERR_ASSERTION]: Input A expected to strictly equal input B:
19:37:06 + expected - actual
19:37:06
19:37:06 - 'EAI_FAIL'
19:37:06 + 'ENOTFOUND'
19:37:06 at ClientRequest.<anonymous> (c:\workspace\node-test-binary-windows\test\parallel\test-http-dns-error.js:48:12)
19:37:06 at ClientRequest.<anonymous> (c:\workspace\node-test-binary-windows\test\common\index.js:379:15)
19:37:06 at ClientRequest.emit (events.js:198:13)
19:37:06 at TLSSocket.socketErrorListener (_http_client.js:392:9)
19:37:06 at TLSSocket.emit (events.js:198:13)
19:37:06 at emitErrorNT (internal/streams/destroy.js:91:8)
19:37:06 at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
19:37:06 at process._tickCallback (internal/process/next_tick.js:63:19)
I think that the errCode could be made an array of strings instead of being set to a string to allow for multiple acceptable error codes.