Add references to Windows 20H2 test images.

[jeremyje]

No description provided.

[k8s-ci-robot]

Hi @jeremyje. 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.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[theopenlab-ci]

Build succeeded.

• containerd-build-arm64 : SUCCESS in 5m 53s (non-voting)

[thaJeztah]

Thanks! Looks like you forgot to sign-off the commit (it's missing a signed-off-by line in the commit message); https://github.com/containerd/project/blob/master/CONTRIBUTING.md#sign-your-work

[theopenlab-ci]

Build succeeded.

• containerd-build-arm64 : SUCCESS in 6m 04s (non-voting)

[thaJeztah]

Hmm.. looks like there's some flakiness in other tests (at least, doesn't look related to this PR);

--- FAIL: TestSnapshotterSuite (0.67s)
    --- FAIL: TestSnapshotterSuite/DevMapperUsage (0.66s)
        snapshotter_test.go:141: assertion failed: expression is false: layer2Usage.Size < sizeBytes+256*dmsetup.SectorSize: 1179648 < 1179648
FAIL
FAIL	github.com/containerd/containerd/snapshots/devmapper	39.953s
ok  	github.com/containerd/containerd/snapshots/devmapper/dmsetup	0.639s
ok  	github.com/containerd/containerd/snapshots/native	7.604s
ok  	github.com/containerd/containerd/snapshots/overlay	15.367s
FAIL
Makefile:177: recipe for target 'root-test' failed
make: *** [root-test] Error 1
Error: Process completed with exit code 2.

[thaJeztah]

LGTM

[jeremyje]

/retest

[k8s-ci-robot]

@jeremyje: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[thaJeztah]

/ok-to-test

[thaJeztah]

/retest

[jeremyje]

/retest

[kevpar]

LGTM

[jeremyje]

How do I trigger that test to run again?

[jeremyje]

/retest

[jeremyje]

/retest

[AkihiroSuda]

@jeremyje "Re-run jobs" can be used for restarting GHA https://docs.github.com/en/actions/managing-workflow-runs/re-running-a-workflow

(I already clicked the button)

[thaJeztah]

@AkihiroSuda I think that's only available for users with write access; at least, button doesn't show for me;

[AkihiroSuda]

🤦‍♂️

Then the only available option would be to amend the commit message slightly and push...

[thaJeztah]

Let me try if closing/re-opening still works as a workaround.

[thaJeztah]

yup, that looks to work

[theopenlab-ci]

Build succeeded.

• containerd-build-arm64 : SUCCESS in 6m 42s (non-voting)

[crosbymichael]

LGTM