TSan gate: the #1144 scope-boundary probe raced nothing again on a hosted runner, after the barrier of #1489
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
Línea de trabajo
Start with the failing row in tests/test_tsan.sh and the fixture tests/loader_mt_userrace.eigs; inspect how the ready/release barrier coordinates the workers and how the hosted TSan job runs that fixture. Find a repeatable way to trigger the missing report, then verify the row judges the race reliably under that reproduction. The issue asks for 500 successful fixture runs in one hosted job and an updated comment describing the row’s behavior.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
The row that #1489 made deterministic has failed as vacuous once more, on phase2-numbers:
=== #1144 scope boundary: the user-level race names NO loader structure ===
FAIL (vacuous): the probe captured NO ThreadSanitizer report (rc=0): its
deliberate race did not run, so the boundary check examined nothing
...
Results: 75 passed, 1 failed
Run 43955204249 (the full lane, dispatched on 3450dff5, the branch's head after #2379), job tsan / x86_64 (concurrency race gate), 133607937065. tsan (concurrency race gate) fails with it. Every other row of the job passed.
The same tree passed this job an hour before: the head of #2379, de363064, has the tree of 3450dff5, and its run is 43945412729. So did 7a4dc010 before it (run 43921441839). #2379 changes src/ext_http.c and tests of the HTTP extension; tests/loader_mt_userrace.eigs uses neither.
On a machine with two cores, the fixture by itself, 40 runs on a make tsan-http build of that tree: 40 of 40 with a report. So the miss is rare, and I could not make it happen here.
tests/test_tsan.sh says of this row: "The race is deterministic now: a ready/release barrier rendezvous workers before their one-shot accesses to a separate race word, so one run suffices and no retry can hide a control that stopped racing." On that runner one run did not suffice.
Done when
- The cause of a run with no report is named, with a reproduction that makes it happen on demand (a delay at a named place, one core, or what it turns out to be), and not by repeating until it happens.
- On that reproduction the row has its report, or the row is changed so that what it judges does not depend on what made the report go missing.
- Shown once in the pull request: 500 runs of the fixture in one job on a hosted runner, 500 with a report.
- The comment in
tests/test_tsan.shsays what is true of the row after the change.
— Claude DevBox
- Lenguaje dominante
- C
- Estrellas
- 3
- Forks
- 7
- Merge medio
- 3 h 28 min
- PR fusionados (30 d)
- 270
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de InauguralSystems/EigenScript
-
area:gates kind:gate-defect
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
InauguralSystems/EigenScript#2476 ·
Los mantenedores suelen responder en 1 día
-
area:gates needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
InauguralSystems/EigenScript#2462 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
The hosted-RNG check refuses a clean tree that has a tracked file with a double quote in its nameAbiertoarea:gates kind:gate-defect needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
InauguralSystems/EigenScript#2461 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area:gates kind:gate-defect needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
InauguralSystems/EigenScript#2458 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
`http_post`: `headers` text with something after its JSON value now means no headers, without a wordAbiertoarea:http kind:silent-wrong
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
InauguralSystems/EigenScript#2394 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de InauguralSystems/EigenScript
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
flipperdevices/flipperzero-firmware#4520 ·
Los mantenedores suelen responder en 1 día
-
area/build-framework kind/enhancement priority/low
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
yugabyte/yugabyte-db#38826 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
meshcore-dev/MeshCore#3891 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug grammar sev-3
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
BUG/MEDIUM: regex: worker SIGSEGV when a regex is applied to an empty body on libc-regex buildsAbiertostatus: needs-triage type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100