CI: https://ci.nodejs.org/job/node-test-pull-request/23927/

@jasnell @Trott the failed tests doesn't seem to be related to the changes of this PR. Can we rerun the CI process?

CI: https://ci.nodejs.org/job/node-test-pull-request/24032/

@jasnell @Trott the failed tests doesn't seem to be related to the changes of this PR. Can we rerun the CI process?

I just started a "resume build" which will re-run just Windows at the same commit/rebase it did 4 days ago. That failure (test-statwatcher) was a very problematic unreliable issue that has since been fixed. If it fails again on the resume-build, we may just want to do a full re-run so that we rebase and get the fix. The problem with doing that right now is that we're having AIX problems in CI and AIX will undoubtedly fail for unrelated reasons. I would expect that AIX issue to get fixed in a few hours (once it's not the middle of the night for the relevant folks with expertise). This is probably too much detail, but the upshot is: If the re-run doesn't pass, feel free to ping again, don't hesitate.

I've added an author ready flag to this which is basically something that a few of us search for every so often to find PRs that are ready to land, so this shouldn't get missed/ignored, but ping anyway. 😀

Landed in e6edd66