Is this both RS1 and RS5, or only RS1 ?

I've only seen this flaky test a big issue on RS1.

i should have started this as a draft PR to run the RS1 tests. i'm putting this to WIP so i can get a temp git commit in to twiddle RS1 tests.

oh right, i can't make changes to jenkinsfile. @thaJeztah can you carry this PR?

@andrewhsu no need to modify the Jenkinsfile; just check the windowsRS1 checkbox when starting a rebuild

From the most recent PR check with 1be272e looks like the TestStartReturnCorrectExitCode test is skipped on RS1:

--- SKIP: TestDockerSuite/TestStartReturnCorrectExitCode (0.01s)
    docker_cli_start_test.go:200: FLAKY on Windows RS1, see #38521

And not skipped for RS5:

--- PASS: TestDockerSuite/TestStartReturnCorrectExitCode (6.54s)

Only the ppc64le unit test failing because of memory allocate failure:

# github.com/docker/docker/daemon/cluster/executor/container.test
/usr/local/go/pkg/tool/linux_ppc64le/link: running gcc failed: fork/exec /usr/bin/gcc: cannot allocate memory

I've rekicked PR check to only run the ppc64le tests and taken the ppc64le node offline so a different one can be used.

I think all the powerpc nodes have 4GB, or are there that have more?

Total Memory: 3.976GiB

Could not connect to ppc64le-ubuntu-13 to send interrupt signal to process
Aborted by Peter Salvatore

That guy again 😂

The ppc64le checks are now also green. I think this PR is ready to go.

Kicked CI again; some weird error while building the image on RS5

 ERROR: make.ps1 failed:
The decryption operation failed, see inner exception.
 At C:\gopath\src\github.com\docker\docker\hack\make.ps1:440 char:13
+             Invoke-WebRequest $url -OutFile "docker.zip"
 +             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~