mirror of
https://github.com/Kpa-clawbot/meshcore-analyzer.git
synced 2026-06-25 19:32:01 +00:00
0712c5ff31
Master CI's Go test job has been timing out at the default 10 minutes since #1655 (`825b2648`) landed additional endpoint-coverage + race tests. This bumps the explicit `-timeout` on both `cmd/server` and `cmd/ingestor` test steps to 15 minutes. No code/test changes — config-only. This is preventative; the slow tests are a separate follow-up. ### Timing data (local sandbox, arm64, slower than CI) | Module | Duration | |---|---| | `cmd/server` (`go test -race ./...`) | **9m 30s** — already grazing the 10m default | | `cmd/ingestor` (`go test ./...`) | 2m 44s | The server suite is now consistently above 9 minutes and any test added on top of #1655 pushes it past 10m on slower CI runners (the failure mode we hit on master). ### Change ```diff - go test -race -coverprofile=server-coverage.out ./... + go test -timeout 15m -race -coverprofile=server-coverage.out ./... - go test -coverprofile=ingestor-coverage.out ./... + go test -timeout 15m -coverprofile=ingestor-coverage.out ./... ``` Out of scope: optimizing the slow tests (TestGetChannelMessagesPerfLargeChannel etc.) — separate issue/PR. Co-authored-by: corescope-bot <bot@corescope>