mirror of
https://github.com/nodejs/node.git
synced 2026-11-09 15:11:11 -05:00
Brian White
3809126427
Before this commit, it was possible on Windows for the server's 'connection' handler to be called *after* the client socket's 'connect' handler. This caused the 'message' event to be missed and the test would never end (timing out in CI). This problem was more easily reproducible on a low resource (slow CPU) Windows (2012r2) installation. This commit waits until both handlers have been called before sending the handle to the master process. Fixes: https://github.com/nodejs/node/issues/3957 PR-URL: https://github.com/nodejs/node/pull/4444 Reviewed-By: Rich Trott <rtrott@gmail.com>
24 lines
669 B
Plaintext
24 lines
669 B
Plaintext
prefix parallel
|
|
|
|
# To mark a test as flaky, list the test name in the appropriate section
|
|
# below, without ".js", followed by ": PASS,FLAKY". Example:
|
|
# sample-test : PASS,FLAKY
|
|
|
|
[true] # This section applies to all platforms
|
|
|
|
[$system==win32]
|
|
test-cluster-shared-leak : PASS,FLAKY
|
|
test-debug-no-context : PASS,FLAKY
|
|
test-tls-ticket-cluster : PASS,FLAKY
|
|
|
|
[$system==linux]
|
|
test-http-client-timeout-event : PASS,FLAKY
|
|
test-child-process-buffering : PASS,FLAKY
|
|
test-child-process-exit-code : PASS,FLAKY
|
|
|
|
[$system==macos]
|
|
|
|
[$system==solaris] # Also applies to SmartOS
|
|
|
|
[$system==freebsd]
|