Intermittent parallel/test-http-regr-gh-2821 failure on V6.9.2 (Windows)

[Akpotohwo]

Version: 6.9.2
Platform: 32-bit (Win2012)

=== release test-http-regr-gh-2821 ===
Path: parallel/test-http-regr-gh-2821
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: read ECONNRESET
    at exports._errnoException (util.js:1022:11)
    at TCP.onread (net.js:569:26)
Command: C:\node\node\out\Release\node.exe C:\node\node\test\parallel\test-http-regr-gh-2821.js

We're seeing this failure intermittently on Windows.

[gibfahn]

@nodejs/platform-windows

[Trott]

FWIW, there is at least one existing "tolerate ECONNRESET on Windows" workarounds in our tests:

node/test/parallel/test-child-process-fork-regr-gh-2847.js

Lines 18 to 24 in eceef76

	if (common.isWindows) {
	s.on('error', function(err) {
	// Prevent possible ECONNRESET errors from popping up
	if (err.code !== 'ECONNRESET')
	throw err;
	});
	}

If the cause gets sorted out for this file, maybe the workaround can be removed from that one.

[bzoz]

@Akpotohwo are you running the tests inside a virtual machine?

[Akpotohwo]

@bzoz Yes I am

[bzoz]

That could be related to a bug in virtualbox 5.0.28 and 5.1.8: https://www.virtualbox.org/ticket/16084. Also you can try this: https://support.microsoft.com/en-us/help/981344/an-application-may-receive-the-10054-error-when-the-application-receives-data-from-a-connection-on-a-computer-that-is-running-windows-7-or-windows-server-2008-r2-if-a-tdi-filter-driver-is-installed

[refack]

Another sighting: #12621 (comment)

23	parallel/test-child-process-fork-regr-gh-2847	
duration_ms	
0.313
severity	
fail
stack	
c:\workspace\node-test-binary-windows\RUN_SUBSET\1\VS_VERSION\vcbt2015\label\win10\test\parallel\test-child-process-fork-regr-gh-2847.js:61
            throw err;
            ^

Error: write EMFILE
    at exports._errnoException (util.js:1026:11)
    at ChildProcess.target._send (internal/child_process.js:663:20)
    at ChildProcess.target.send (internal/child_process.js:547:19)
    at Worker.send (internal/cluster/worker.js:54:28)
    at Socket.<anonymous> (c:\workspace\node-test-binary-windows\RUN_SUBSET\1\VS_VERSION\vcbt2015\label\win10\test\parallel\test-child-process-fork-regr-gh-2847.js:33:14)
    at Object.onceWrapper (events.js:312:19)
    at emitNone (events.js:105:13)
    at Socket.emit (events.js:207:7)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1102:10)

FWIW https://ci.nodejs.org/job/node-test-binary-windows/8042/RUN_SUBSET=1,VS_VERSION=vcbt2015,label=win10/ (I don't know how long there are cached)

[gibfahn]

@refack that looks like a different test (parallel/test-http-regr-gh-2821 vs
parallel/test-child-process-fork-regr-gh-2847)

[refack]

@refack that looks like a different test (parallel/test-http-regr-gh-2821 vs
parallel/test-child-process-fork-regr-gh-2847)

As far as I recall the underlying problem was suggested to be the same #3635 (comment)

[gibfahn]

I don't think #12698 fixed this, as @gireeshpunathil mentions in #3635 (comment) , there are three errors, #12698 fixes the EMFILE one. I'm still seeing this locally.

[Trott]

This test no longer exists. (It has probably been renamed.) Closing.