Disable "Test spawning a lot of tasks" on Windows

[tkf]

This patch disables the known failure #43124 on Windows for now.

Ref: #43072 (comment)

[DilumAluthge]

Instead of disabling completely, it might be fine to just dump all the output to the log. Then, the next time we see this failure in CI, we can actually collect some information on why it failed.

[DilumAluthge]

I also don't object to disabling it completely on Windows. Either approach is fine.

[tkf]

Yeah, maybe we can just pull only the first commit. I guess it'd be easier to notice the failure if the CI actually fails.

[tkf]

Let's pull in the first commit via #43126 first. Then I'll prepare a patch to disable the Windows test (without the logging message #43125 (comment)) in this PR. This way, we can disable the Windows test with a few clicks.

[tkf]

Never mind, this is pretty reproducible. I get the log output

┌ Error: Failed test: "spawn and wait *a lot* of tasks in @profile" (n = 2000000)
│ 
...
│   proc.exitcode = 3221225477
│   proc.termsignal = 0

in https://build.julialang.org/#/builders/65/builds/5543

3221225477 is STATUS_ACCESS_VIOLATION so there's something wrong. But it looks like there's no backtrace.

Note that n = 2000000 is the largest number of tasks in the test. I wonder if ignoring this case is sufficient.

BTW, #32938 would have been helpful for noticing this from the vanilla test output.

[DilumAluthge]

Note that n = 2000000 is the largest number of tasks in the test. I wonder if ignoring this case is sufficient.

Let's go ahead and give this a try?

[tkf]

So, there seem to be a failure with n < 2000000: https://build.julialang.org/#/builders/65/builds/5597/steps/5/logs/stdio

Let's skip the tests on Windows. Decreasing n maybe could make it less frequent but it'd make it just more annoying.