ci: run test-go-pg mise tool install under bash on Windows - #27483
Merged
nickvigilante merged 1 commit intoAug 3, 2026
Conversation
The "Install Go mise tools" step in the test-go-pg job had no `shell:`, so on the windows-2022 matrix leg it ran under PowerShell while `./.github/scripts/retry.sh` is a bash script. The step silently no-oped, so `mtimehash` was only present when the mise tool cache was warm. On a cache miss, the "Normalize File and Directory Timestamps" step then failed with `mtimehash: command not found` (exit 127) before any tests ran. Pin the step to `shell: bash` so the install actually runs on Windows and repairs a cache miss. DOCS-605 > This PR was created with AI assistance (Coder Agents).
johnstcn
approved these changes
Jul 26, 2026
nickvigilante
deleted the
vigilante/docs-605-fix-test-go-pg-windows-2022-ci-failure-mtimehash-missing-on
branch
August 3, 2026 14:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Add
shell: bashto theInstall Go mise toolsstep in thetest-go-pgjob so it runs under Git bash on thewindows-2022matrix leg.Why
test-go-pg (windows-2022)has been failing in the Normalize File and Directory Timestamps step with:before any tests run, which trips the aggregate
requiredgate.Root cause: the
Install Go mise toolsstep had noshell:, so on Windows it ran under PowerShell, while./.github/scripts/retry.shis a bash script (#!/usr/bin/env bash). The step silently no-oped on Windows (zero output), somtimehashwas only present when the mise tool cache was warm. On a cache miss it was never installed, and the normalize step failed with exit 127.mainstays green only because the cache is usually warm — both green and failing runs use the samedepot-windows-2022-16runner, so this is not a fork/runner-routing issue.Pre-existing CI-tooling issue, unrelated to the change that surfaced it (a Helm-only community PR, #27360).
Fix
One line: pin the step to
shell: bashso the install actually runs on Windows and repairs a cache miss instead of being silently skipped.Verification
Local proof that the step's install target builds and
mtimehashruns under bashFinal confirmation is this PR's own
test-go-pg (windows-2022)run. Note: if the mise cache is warm on this run the job passes regardless; the fix specifically hardens the cache-miss path this step exercises on Windows.Follow-up (not in this PR)
mtimehashis absent / invoke viamise exec) so a missing cache optimizer can't hard-fail the job.run:steps that invokeretry.sh/bash scripts withoutshell: bash.Linear: DOCS-605