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

Abierto
#3,306 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
15/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
go, javascript
Área
ci-cd, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Go
Estrellas
97
Forks
61
Merge medio
4 h 14 min
PR fusionados (30 d)
913

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de opensro-dev/opensro

Todos los issues de opensro-dev/opensro

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.