30291040628
68%
master: 100%

Ran 27 Jul 2026 05:51PM UTC

Jobs 1

Files 28

Run time 1min

Badge

Embed ▾

Committed 27 Jul 2026 05:50PM UTC coverage: 65.017%. Remained the same

Build # 30291040628

Build Type

push

github

Committed by

maguro

Commit Message

Warm Windows Go build/tool caches before test timeout

The `go test -timeout 30s` step was regularly failing only on
windows-latest: internal/generator's TestGenerator suite shells out to
`go tool wire gen`, and the tool's first-time compile of the wire
binary consistently pushes that package past the 30s budget on
Windows, even though the same suite is comfortably fast on Linux and
macOS.

Add a preceding step that primes the caches setup-go persists across
runs: `go build -race ./...` for the module's own packages, and
`go tool wire --help` to force the wire tool's module download and
binary compile, since it's a go.mod tool dependency never reached by
an ordinary build. Keeping the timeout on the test step itself, rather
than raising it, means it still bounds only the behavior we actually
mean to assert on.

Coverage Stats

959 of 1475 relevant lines covered (65.02%)

37.13 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	30291040628.1	27 Jul 2026 05:50PM UTC	28	65.02	GitHub Action Run

livetribe / yama / 30291040628
68%
master: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 30291040628

livetribe / yama / 30291040628 68% master: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 30291040628

livetribe / yama / 30291040628
68%
master: 100%

README BADGES
x