kubernetes/minikube

ci: Ensure workflow timeouts - runs can get stuck for hours

Closed

#23,041 opened on May 25, 2026

View on GitHubContributor guide
 (23 comments) (0 reactions) (1 assignee)Go (5,222 forks)batch import
area/testinggood first issuehelp wanted

Repository metrics

Stars
 (31,799 stars)
PR merge metrics
 (Avg merge 12d 19h) (43 merged PRs in 30d)

Description

This run was stuck for 6 hours! in the apt-get install step https://github.com/kubernetes/minikube/actions/runs/26373054430/job/77628725110?pr=23040

Fix

  • Set job level timeout
  • Set step level timeout

Job level timeout

jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 30

Step level timeout

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - name: Run complex tests
        run: ./run-tests.sh
        timeout-minutes: 10

For the next step see #23043.

Contributor guide

Research direction
Add timeout minutes to the CI workflow steps and jobs as shown in the issue description.
Tech stack
go
Domain
ci cddevops
Issue type
DevOps
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90