Hi @gabriel-samfira. 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.

The downgrade steps are pretty long lived.. Says it took 8m 30s on the ws2022 run 😐

The downgrade steps are pretty long lived.. Says it took 8m 30s on the ws2022 run neutral_face

The default Github runners are not that beefy, unfortunately. It takes a while to download+install+generate the shims. Will let them finish before sending the update with the comment to the Downgrade step.

The downgrade steps are pretty long lived.. Says it took 8m 30s on the ws2022 run 😐

I was worried about hitting the timeout but looks like we have it at 50m for Windows integration runs and at 33m we are on the last 2 steps, so at least that part should be fine (and this is on ws2022 which took 3.5 minutes longer for the downgrade than 2019)

Looks like the ThreadSanitizer issue didn't pop up. Adding the comment and pushing.