Ouch! Should we skip on that platform?

cc @ShogunPanda

I don't know why it only started failing (frequently) recently. I don't see any related changes in the commit history.

Where do we source our Windows machines? I've seen a significant degradation in performance for GitHub Actions on Windows (which uses Azure), leading to many of my project to start failing on Windows.

My 2 cents is something has changed on the host and the test is now flaky enough to be a problem (while before it failed spuriously)

cc @nodejs/build

Marking it: #47134

Azure and Rackspace (~50%/50%)

The three failures linked by @tniessen happened on Rackspace machines

@targos Almost all recent builds have failed. Are all of these on rackspace?

I don't know how to check without opening each run one by one.

I don't expect you to do that, of course 😄 And I assume that we couldn't do anything about it even if it was rackspace machines, so let's go ahead with marking it as flaky (or skip if necessary) for now.

According to nodejs/reliability#527 and nodejs/reliability#526, the test did indeed only fail on Rackspace machines. However, given the build trend (see #47116 (comment)), that would mean that Rackspace picked up almost every build.