Fuzz: a viewer known-5xx entry fires on one run and not the next at the same commit and seed

Abierto
  • ¿Algo no está bien?
#1,578 2 comentarios 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-2 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions
Área
ci-cd, testing

Línea de trabajo

Start with the viewer pass of the fuzz workflow, where the per-entry summary is written, and with tests/fuzz/known-5xx.toml, which lists the 15 known entries. The first change is to print the names of the known-with-no-5xx, unlisted-5xx and listed-but-reached entries to the job log as well as the job summary. Done means a red run's log names the quiet entry; the second step, finding why that entry's 5xx varies, needs the run history.

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

Descripción

bug

The fuzz workflow's viewer pass gave two different verdicts for the same commit and the same seed.

  • Run 41328357368, commit 968d9b37, seed 20261006.
    • Attempt 1: viewer ... RED | ... | 5xx operations 14 (not listed 0, known entries 15, of them with no 5xx 1) | reached 72, unreached 172.
    • Attempt 2 (the failed job re-run, nothing else changed): viewer ... GREEN | ... | 5xx operations 15 (not listed 0, known entries 15, of them with no 5xx 0).

So one of the 15 viewer entries in tests/fuzz/known-5xx.toml does not answer 5xx on every run. A listed entry that does not fire turns the pass red, so the scheduled nightly run can go red with no change to the code.

The job log does not say which entry went quiet: the per-entry detail goes only to the job summary, and the run uploads no artifact. Two things would close this:

  1. Print the names of the entries in each category (known with no 5xx, unlisted 5xx, listed but reached) to the job log as well as the summary, so a red run can be diagnosed from its log.
  2. Once the quiet entry is known, find why its 5xx depends on the run (ordering, data left by earlier operations, a timeout) and either make it deterministic or mark it as one that may not fire.
Lenguaje dominante
Python
Estrellas
0
Forks
4
Merge medio
5 h 36 min
PR fusionados (30 d)
509

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 Controlvar/controlvar

Todos los issues de Controlvar/controlvar

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.