check-server: 30s go test budget trips on loaded Windows boxes with every test green

Aberta
#3,306 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-3 horas
Facilidade para iniciantes
15/100
Tipo de issue
Bug
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
go, javascript
Domínio
ci-cd, testing

Direção de pesquisa

The budget check lives in scripts/checks/check_go_server.mjs, and the budget list is scripts/checks/go-test-budget.txt; internal/gates is the package that exceeds 30s locally. The issue says the fix is workstation hygiene, not a code or ledger change, so there is no clear patch to write. Before touching anything, confirm with a maintainer whether any change to the gate is wanted at all.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

area: server bug priority: medium

Observed 2026-11-12 on the laptop workstation during PR #3305's local gates:

  • pnpm task run check:server: every package passes, but the budget step rejects the run - internal/gates measured 36.6s in the full run and 39.5s in the solo re-measure (budget 30s, scripts/checks/check_go_server.mjs).
  • A hand solo run of go test ./internal/gates/ -count=1 took 442s wall with ~1s user+sys CPU: the time is process-start/init stalls (the documented Windows AV-scan pattern on freshly linked test binaries), not test work. The same package's boundary test alone finishes in ~12s including compile.
  • scripts/checks/go-test-budget.txt names only internal/game/action; on CI runners internal/gates is comfortably inside the budget, so this is a workstation-load phenomenon, not package growth.

This is the #2562 class (closed: cannot waive - rerun on a quieter box). Filed so local submissions on a busy box can name an open issue in the gate waiver instead of re-litigating it; the fix, if any, is box hygiene (fewer concurrent suites), not a ledger entry - the ledger can only shrink and CI does not need it.

Linguagem predominante
Go
Estrelas
97
Forks
61
Merge médio
4h 14min
PRs com merge (30d)
913

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de opensro-dev/opensro

Todas as issues de opensro-dev/opensro

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.