Hi @aznashwan. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Full context: the crash we're seeing is consistent and can be seen in all Windows Periodic runs since #6888 merged. (the latest green column was from a test of this PR)

The issue had eluded me while testing #6888 since I had intentionally unset the Google bucket creds so the artifact upload would get skipped in my run in order to not have any junit files uploaded to the bucket, but the the actual test command never errors out, leading to the GitHub actions always being green.

PS: switching from mingw = "11.2.0" to mingw = "11.3.0" still shows the issue, so a downgrade is the only soluion at this point.

@dcantah @kzys @dmcgowan could one of you please have a look over this before the next scheduled Windows CI run tonight?

but the the actual test command never errors out, leading to the GitHub actions always being green.

Can we also fix this one?

@kzys turns out the test command does correctly error out, and the actual culprit was the lack of pipefail in the Windows workflow itself, which I've addressed in #7085.

Unfortunately it looks like MinGW needed an additional downgrade as well, which I've just shoehorned into that PR directly.