Skip to content

ci: extend mise fetch-remote-versions timeout to 120s#204

Open
oyoshot wants to merge 1 commit into
mainfrom
ci/extend-mise-fetch-timeout
Open

ci: extend mise fetch-remote-versions timeout to 120s#204
oyoshot wants to merge 1 commit into
mainfrom
ci/extend-mise-fetch-timeout

Conversation

@oyoshot

@oyoshot oyoshot commented Jun 15, 2026

Copy link
Copy Markdown
Owner

Summary

  • CI が mise install 中に cargo:foo = \"latest\" のバージョン解決で crates.io API がデフォルト 20s でタイムアウトし、3回リトライ全失敗 → ビルド全体が落ちる状態だった (feat(go): manage Go dev tools via mise #203 の CI で再現、main の cron も5週連続 fail)。
  • MISE_FETCH_REMOTE_VERSIONS_TIMEOUT=120sApply chezmoi ステップに渡してタイムアウトを伸ばす。エラーメッセージ自身が示している正規のノブ。
  • arch は sudo -Hu builder env ... を介して chezmoi を起動しているので、env を明示的に伝播させた。

Test plan

🤖 Generated with Claude Code

CI has been failing because `mise install` resolves `cargo:foo = "latest"`
entries by hitting crates.io's `/api/v1/crates/<name>/versions` endpoint,
and the default 20s timeout is exceeded under GitHub Actions network
conditions. Three internal retries all time out, so the whole `cargo:`
batch fails — even though no `cargo:` entry was touched.

Bump to 120s via `MISE_FETCH_REMOTE_VERSIONS_TIMEOUT` (the same env var
mise's own error message points to). Pass it through arch's
`sudo -Hu builder env` so the builder process sees it too.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant