Investigate flaky parallel/test-stdio-pipe-redirect

[joyeecheung]

Refs: nodejs/reliability#14

Reason	parallel/test-stdio-pipe-redirect
Type	JS_TEST_FAILURE
Failed PR	3 (#22320, #22202, #21593)
Appeared	test-azure_msft-win10-x64-1, test-rackspace-win2008r2-x64-1, test-azure_msft-win2012r2-x64-2, test-rackspace-win2012r2-x64-2, test-azure_msft-win2016-x64-2, test-azure_msft-win10-x64-4, test-rackspace-win2012r2-x64-1, test-azure_msft-win2016-x64-4, test-azure_msft-win10-x64-3, test-rackspace-win2012r2-x64-9, test-azure_msft-win2012r2-x64-1
First CI	https://ci.nodejs.org/job/node-test-pull-request/16458/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/16489/

Example

not ok 360 parallel/test-stdio-pipe-redirect
  ---
  duration_ms: 0.599
  severity: crashed
  stack: |-
    oh no!
    exit code: CRASHED
  ...

[joyeecheung]

This looks like v8.x only, and windows-only

[joyeecheung]

A more detailed stack

URL        https://ci.nodejs.org/job/node-test-binary-windows/COMPILED_BY=vs2015-x86,RUNNER=win2012r2,RUN_SUBSET=1/19259/console
Type       JS_TEST_FAILURE
Built On   test-rackspace-win2012r2-x64-2
Reason
  not ok 360 parallel/test-stdio-pipe-redirect
    ---
    duration_ms: 0.703
    severity: fail
    stack: |-
      Assertion failed: 0, file c:\workspace\node-compile-windows\deps\uv\src\win\req-inl.h, line 214
    ...

[MylesBorins]

@joyeecheung I think I landed a fix for this one. It shouldn't be showing up anymore

[joyeecheung]

@MylesBorins Thanks, do you know which commit fixed that?

[MylesBorins]

I believe it is related to 2ec981b

It should have been landed before the test landed on 8.x