-
Notifications
You must be signed in to change notification settings - Fork 594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix broken TestImageInspectDifferentValidReferencesForTheSameImage #3483
Conversation
cc @AkihiroSuda Tagging @manugupt1 Review at your convenience. |
061a0d9
to
f40cc41
Compare
@@ -71,16 +70,12 @@ func TestImageInspectSimpleCases(t *testing.T) { | |||
func TestImageInspectDifferentValidReferencesForTheSameImage(t *testing.T) { | |||
nerdtest.Setup() | |||
|
|||
platform := runtime.GOOS + "/" + runtime.GOARCH |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Earlier version of this test was using linux/amd64, because it was hardcoding the sha.
When I rewrote the test a few weeks ago, I removed the static sha and replaced by a lookup, allowing to use whatever platform - though I did not remove the platform mechanism itself for some reason.
It is unnecesary.
f40cc41
to
839f957
Compare
Could you update the commit message to explain why |
CI is green-ish (Docker failure is unrelated and will get fixed in #3464). |
As of 10/01/2024, busybox latest tag (1.37.0) is no longer the same thing as stable (1.36.1). It is unclear if that was made on purpose, or a problem with Docker publication process. Signed-off-by: apostasie <spam_blackhole@farcloser.world>
Doing now. |
839f957
to
c661d16
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
Fix #3479
Reviewers: since the official
busybox
is a moving target, and has just shifted under our feet, I replaced it with a copy underapostasie/busybox
.This is a short term fix so that the CI does not stay bust - but I do not like the idea of having images in my personal account.
(Part of) the current intent of this test was apparently to test variants of image names only available on the hub.
To get rid of my images here, here are our options: