Evaluate selecting test configs separately for each confidence level

Abierto
  • ¿Algo no está bien?
#7,386 0 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
machine-learning

Línea de trabajo

Start by locating the HTTP service that returns config_groups, the config selection model evaluation, and the Firefox taskgraph strategies named bugbug-reduced-manifests-config-selection-*. Measure selection cost and regressions caught for each level against a selection using only groups at or above that level. The issue is resolved when the measurements show whether separate per-level selections are worthwhile and, if so, the service replies and taskgraph strategies use them.

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

Descripción

The HTTP service selects the configs of each confidence level (very_high, high, medium, low, very_low) after the ones of the levels above, reusing them, and returns a single config_groups for all levels. The Firefox taskgraph strategies that select configs (bugbug-reduced-manifests-config-selection-*) run the groups at or above their level on these configs.

This keeps the configs of a level independent from the groups below it, which don't run with it. However, a strategy at a lower level runs the groups of the levels above too, and their configs were selected without knowing which configs the lower groups would use: e.g. for the low strategy, a medium group can't reuse a config selected for a low group, so the low strategy may run more configs than a selection made for its groups alone.

We should measure how much this costs, e.g. in the config selection model's evaluation, comparing the cost and the regressions caught at each level with a selection made for the groups at or above it only.

If the difference is significant, the HTTP service could return a separate config selection for each level (a selection over all the groups at or above it), and the taskgraph strategies could read the one for their level. This would increase the size of the replies and the number of config selection model calls, and require changes in the taskgraph.

Lenguaje dominante
Python
Estrellas
578
Forks
366
Merge medio
2 d 19 h
PR fusionados (30 d)
136

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 mozilla/bugbug

Todos los issues de mozilla/bugbug

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.