kubernetes/minikube

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

Open

#23,041 建立於 2026年5月25日

在 GitHub 查看
 (10 留言) (0 反應) (2 負責人)Go (31,799 star) (5,222 fork)batch import
area/testinggood first issuehelp wanted

描述

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.

貢獻者指南

技術棧
github actionsshell
領域
devopscloud
議題類型
devops
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic knowledge of GitHub Actions YAML
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
80
研究方向
Examine the CI workflow file in the repository (likely `.github/workflows/`) and identify the job or step that runs `apt get install`. Add `timeout minutes: 30` at the job level or `timeout minutes: 10` at the step level to prevent long hangs. Reference the example in the issue and consider following up on #23043 for next steps.
ci: Ensure workflow timeouts - runs can get stuck for hours · kubernetes/minikube#23041 | Good First Issue