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

a worker was handed no note at all under a loaded full-tree run

Abierto
  • ¿Algo no está bien?
#1,375 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
testing-qa

Línea de trabajo

Start with TestTwoWorkersLiveAtOnceEachGetOnlyItsOwnNote in internal/run/note_channel_test.go and reproduce the package with -race, then compare it with the full-tree run described at commit 2f94ca1f0. Trace the two workers' note delivery decisions and improve the failure output to identify each worker's notes and timing. Done means the runtime or fixture issue is fixed, the change explains which it was, and package -race covers it in CI.

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

Descripción

area:tests bug sev:papercut

What happened

TestTwoWorkersLiveAtOnceEachGetOnlyItsOwnNote in internal/run failed once,
inside a run of 112 packages at once on a loaded build box.

--- FAIL: TestTwoWorkersLiveAtOnceEachGetOnlyItsOwnNote (0.66s)
    note_channel_test.go:326: alpha was handed its own note 0 times, want once
FAIL	github.com/Agent-Field/codeaf/internal/run	29.998s

The dump the assertion prints shows three requests to alpha, each carrying the
work order and the ask, and none of them carrying the note. So the note was not
delivered late or delivered to the wrong worker in that run. It was not there at
all across every request the worker made.

It does not reproduce, and that is the report

Sixteen attempts on the same tree at the same commit, on a box at load 0.33:

what result
-count=5 -run TestTwoWorkersLiveAtOnce ./internal/run/ ok 2.758s
-count=3 ./internal/run/ (whole package, so the other tests run beside it) ok 75.353s
GOMAXPROCS=1 -count=8 -run TestTwoWorkersLiveAtOnce ./internal/run/ ok 4.151s

Filing rather than rerunning is deliberate. The repository's own rule is that a
test failing only when other suites run beside it is a bug report and not a
known shape, and this test is about two workers being live at once, which is the
condition a loaded box actually supplies and an isolated rerun does not.

It is NOT in .github/known-red.txt and must not be added to it.

Why it matters more than an ordinary flake

The behaviour under test is the one #1356 shipped: a note is a channel into a
running worker rather than a log nobody reads. A worker that never receives its
note is that feature not working, and the failing case renders exactly like a
run where nobody sent a note. If this is real, the product symptom is silence.

Replication

Not reliable. What produced it once: go test -count=1 over every package
except internal/tui3 and internal/session on one box, roughly 112 packages,
during a full-tree check. The commit was 2f94ca1f0.

Acceptance

  1. Whatever the cause, the test's failure output says which of the two workers
    got which notes and when, not only that alpha got none. The current dump
    shows the requests but not the delivery decisions, so a reader cannot tell a
    note that was never written from one written to the wrong worker.
  2. If it is a race in the runtime, -race on this package in CI names it.
  3. If it is a race in the fixture, the fixture is fixed, and the change says
    which of the two it was. Not "made deterministic".
Lenguaje dominante
Go
Estrellas
115
Forks
14
Merge medio
9 h 38 min
PR fusionados (30 d)
749

Preparar el entorno

Aún no hemos revisado los archivos de configuración de este proyecto. Empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 Agent-Field/CodeAF

Todos los issues de Agent-Field/CodeAF

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.