CI run #53 timed out after 3 hours because go test ./... hangs waiting for proxy.golang.org which is unreachable from the runner.
Additionally the workflow used go-version: 1.23 while go.mod requires go 1.24.0.
Changes
go mod vendor — all dependencies are now committed; no outbound network needed during CI
GOFLAGS: -mod=vendor set at job level so all go commands use vendor/
go-version corrected from 1.23 → 1.24.0 to match go.mod
GOTOOLCHAIN: local moved to job-level env: block (was per-step inline, prone to shell escaping issues)
cache: false on setup-go (module cache is irrelevant when vendoring)
timeout-minutes: 15 added to the test job so failures are caught in minutes, not 3 hours
Fixes HAN-414
## Problem
CI run #53 timed out after 3 hours because `go test ./...` hangs waiting for `proxy.golang.org` which is unreachable from the runner.
Additionally the workflow used `go-version: 1.23` while `go.mod` requires `go 1.24.0`.
## Changes
- `go mod vendor` — all dependencies are now committed; no outbound network needed during CI
- `GOFLAGS: -mod=vendor` set at job level so all `go` commands use `vendor/`
- `go-version` corrected from `1.23` → `1.24.0` to match `go.mod`
- `GOTOOLCHAIN: local` moved to job-level `env:` block (was per-step inline, prone to shell escaping issues)
- `cache: false` on `setup-go` (module cache is irrelevant when vendoring)
- `timeout-minutes: 15` added to the `test` job so failures are caught in minutes, not 3 hours
Fixes HAN-414
- Run go mod vendor to eliminate proxy.golang.org network dependency
- Set GOFLAGS=-mod=vendor at job env level so all go commands use vendor/
- Fix go-version from 1.23 to 1.24.0 to match go.mod
- Move GOTOOLCHAIN=local to job-level env (not per-step inline)
- Set cache: false on setup-go (cache is irrelevant with vendoring)
- Add timeout-minutes: 15 so failures are caught quickly instead of 3h
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: multica-agent <github@multica.ai>
Switch from hardcoded go-version: '1.24.0' to go-version-file: go.mod
so the CI Go version always stays in sync with the module's go directive.
All tests pass locally with GOFLAGS=-mod=vendor GOTOOLCHAIN=local.
Re-triggering CI run after previous run 1504 timed out on toolchain download.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: multica-agent <github@multica.ai>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
CI run #53 timed out after 3 hours because
go test ./...hangs waiting forproxy.golang.orgwhich is unreachable from the runner.Additionally the workflow used
go-version: 1.23whilego.modrequiresgo 1.24.0.Changes
go mod vendor— all dependencies are now committed; no outbound network needed during CIGOFLAGS: -mod=vendorset at job level so allgocommands usevendor/go-versioncorrected from1.23→1.24.0to matchgo.modGOTOOLCHAIN: localmoved to job-levelenv:block (was per-step inline, prone to shell escaping issues)cache: falseonsetup-go(module cache is irrelevant when vendoring)timeout-minutes: 15added to thetestjob so failures are caught in minutes, not 3 hoursFixes HAN-414
Pull request closed