kubernetes/minikube

Skip TestAddons/parallel/Registry to unblock developement

Open

#23,044 opened on May 25, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (31,799 stars) (5,222 forks)batch import
area/addonsarea/testinggood first issuehelp wanted

Description

Same test pass in Jenkins but prow build is required. Need to investigate the failure, we may need to fix the test or the code.

High priority since this break required tests, preventing merge of other PRs. Currently merge requires admin rights because of this issue.

Example failure: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/minikube/23036/pull-minikube-docker-docker-linux-x86/2058557131707125760

Plan:

  • Skip the test with a message linking to this issue

See #23036 for example PR.

Contributor guide

Tech stack
godockerkubernetes
Domain
testingci cd
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go basicsTest skip syntax
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
The issue requires skipping the test TestAddons/parallel/Registry in the minikube repository. The PR #23036 provides an example of how to skip a test. Look for the test file in the minikube codebase (likely under test/ or integration/). Add a t.Skip() call with a message referencing this issue (#23044) and ensure the skip is conditional or unconditional as per the plan. After skipping, verify the test is excluded from CI runs.