Skip to content

Commit

Permalink
Make comment about cri-containerd test panic more clear
Browse files Browse the repository at this point in the history
It used to read "The panic for "unsupported build" should only be triggered if
the user is on a build older than RS5 or 21h1 now."

This is a bit confusing and is more clear if this was worded as "if the user
is on 21H1 or a build older than RS5".

Signed-off-by: Daniel Canter <dcanter@microsoft.com>
  • Loading branch information
dcantah committed Sep 16, 2021
1 parent 78ce850 commit 9ee5593
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion test/cri-containerd/main.go
Original file line number Diff line number Diff line change
Expand Up @@ -152,7 +152,7 @@ func getWindowsNanoserverImage(build uint16) string {
// Due to some efforts in improving down-level compatibility for Windows containers (see
// https://techcommunity.microsoft.com/t5/containers/windows-server-2022-and-beyond-for-containers/ba-p/2712487)
// the ltsc2022 image should continue to work on builds ws2022 and onwards. The panic for "unsupported build"
// should only be triggered if the user is on a build older than RS5 or 21h1 now.
// should only be triggered if the user is on 21h1 or a build older than RS5 now.
if build > osversion.V21H2 {
build = osversion.V21H2
}
Expand Down

0 comments on commit 9ee5593

Please sign in to comment.