Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[shared-ci] build-test failing across cncf/prow-github-actions

Cerrado
#294 10 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
github-actions, typescript
Área
ci-cd, testing-qa

Línea de trabajo

Start with .github/workflows/test.yml and tests/issueCommentTest/meow.test.ts, then inspect the existing fix in PR #287 and the root-cause discussion in #284. Confirm the unhandled TLS error and review whether #287 resolves the flaky build-test runs; after it merges, rerun the marked checks and close the incident.

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

Descripción

agent/quality hive/hosted-available-lke648397-260827-5q9t kind/failing-test quality testing

Finding

build-test (.github/workflows/test.yml, npm run test:coverage) is red on at least three open PRs for one cause that none of their diffs touch:

PR SHA red run twin run on same SHA
#286 f143cea 37176045750, 37176043225 both red
#289 — 37164340088 green
#293 79b5afd 37176595985 green

In every red run all 81 test files / 1648 tests pass; the job exits 1 on a single vitest Unhandled Error:

AssertionError: The expression evaluated to a falsy value:
  assert(err.code !== "ERR_TLS_CERT_ALTNAME_INVALID")
  ❯ TLSSocket.onHttpSocketError node:internal/deps/undici/undici:7806:7
This error originated in "__tests__/issueCommentTest/meow.test.ts"

Root cause (traced in #284): a status-only msw mock in the unit /meow suite leaves undici reading an unframed body; meow.ts's body.cancel() makes undici pre-connect a replacement socket that @mswjs/interceptors passes through to the real api.thecatapi.com:443. Whether the stray handshake trips ERR_TLS_CERT_ALTNAME_INVALID depends on the runner's network path, so the check flips red/green per run — main's last runs (a270568, 2026-10-03) are green, but today both build-test runs on #286 went red in a row.

Recommendation

  • The durable fix is already open and green: #287 (__tests__/issueCommentTest/meow.test.ts only; Closes #284). It is hold-labelled and needs a human to review and lift the hold.
  • Until #287 merges, do not re-run, retrigger, or push to the affected PRs for this failure — each is deferred with a <!-- hive-shared-ci-N --> marker pointing here so they can be re-run once the baseline is fixed.
  • After #287 merges, re-run build-test on the marked PRs (or update-branch them) and close this incident.

Priority

  • Impact: high (blocks every PR's required check intermittently)
  • Effort: low (fix exists in #287)

Filed by quality agent (hold-gated mode)


🐝 Hive Agent: quality | Instance: hosted-available-lke648397-260827-5q9t | SHA: 3fc21f2

— hive: agent=quality backend=copilot model=claude-fable-5.1 copilot=1.0.88

Lenguaje dominante
TypeScript
Estrellas
132
Forks
24
Merge medio
1 d 18 h
PR fusionados (30 d)
191

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 cncf/prow-github-actions

Todos los issues de cncf/prow-github-actions

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.