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
explicitly fail if no images are found when running remote tests #91470
Conversation
The previous implementation succeeds if no images are run. This causes silent failures when image matchers are provided that do not match any image.
Nice, that's what I expected to see. Looks like I can debug by whack-a-mole if necessary. |
@MHBauer Thank you for the PR. 2 observations:
Thoughts? |
I think failing is informing. Can we configure test-infra image bumper to look at cos? |
i agree failing loudly is preferred. /retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: derekwaynecarr, MHBauer The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
@@ -244,6 +244,10 @@ func main() { | |||
klog.Fatalf("Could not retrieve list of images based on image prefix %q and family %q: %v", | |||
imageConfig.ImageRegex, imageConfig.ImageFamily, err) | |||
} | |||
if len(images) == 0 { // if we have no images we can't run anything |
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.
It will be cleaner to put this into the function rather than outside. See #91543
/retest Review the full test history for this PR. Silence the bot with an |
The previous implementation succeeds if no images are run. This causes
silent failures when image matchers are provided that do not match any image.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Which issue(s) this PR fixes:
Some of the root cause of this existing in the first place.
#91292
In this issue we can see that in april some images were updated, and tests stopped running at all for 2 of 3 images.
Special notes for your reviewer:
With a list of no images, it turns a bunch of the later for loops into nops, because we
for _,_ := range
over an empty container.Ya'll looked at the issue:
/cc @spiffxp @vpickard @bart0sh @dims
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
I think tests should fail if they don't run.
I'm not sure how to test this.
This has potential to cause anything using image-regex, image_regex, image-family, image_family matchers to fail loudly.
/hold