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

Dependency only tasks should run with maximum allowed priority of their dependents

Abierto
#625 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python
Área
ci-cd

Línea de trabajo

Start by tracing how the optimized and target graphs are produced and how task priorities are represented. Then inspect how requests to the Taskcluster auth service could obtain the highest allowed priority. Done means dependency-only tasks follow the stated capped maximum-priority algorithm without changing target tasks.

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

Descripción

Tasks that get pulled into the graph only as a dependency should adjust their priority to match the priority of the task(s) that depend on it.

For example, if a test task runs with the lowest priority, the build that it depends on should also be lowest priority. Conversely, if we're in the middle of a chemspill and need to schedule some release tasks with highest priority, the builds that they depend on should also run with highest priority.

In Gecko, we already have the ability to set the priority of an entire graph, so the chemspill case isn't that important. But the lowest case is not currently possible (unless you're willing to make the whole graph lowest). But in general, it would be nice if this tuning of priorities happened automatically and at a much more granular level.

I propose that for all tasks that are in the optimized graph but not the target graph, we set the priority based on the following algorithm:

min(<highest allowed priority>, max(<priorities of dependent tasks>))

Obtaining the <highest allowed priority> would require a request to the Taskcluster auth service. I'm not sure if we'd want the ability to toggle this behaviour on or off. I'd be inclined to make it the default at the very least.

Lenguaje dominante
Python
Estrellas
26
Forks
55
Merge medio
2 d 6 min
PR fusionados (30 d)
15

Guía de contribución

Abrir la guía de contribución

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 taskcluster/taskgraph

Todos los issues de taskcluster/taskgraph

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.