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

fix(performance): go-faster CI numbers mix workflows and fast failures

Cerrado
  • ¿Algo no está bien?
#6,338 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@kyle-sexton ya está trabajando en esto.

Desde el 11/10/2026.

  • #7094 de @kyle-sexton — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
62/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, shell
Área
ci-cd, performance

Línea de trabajo

Locate the /performance:go-faster plugin that currently samples the last 5 completed workflow runs for the ci-cd, gates and tests areas. Change sampling so runs are grouped per workflow (at least the required-check workflow ci.yml) and successful full runs are separated from failed and skipped ones; put workflow name and outcome beside every CI number. Add a test that feeds a mixed run list and asserts per-workflow, success-only medians.

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

Descripción

needs-triage priority: medium

Problem

/performance:go-faster's ci-cd, gates and tests areas sample the repository's last 5 completed workflow runs regardless of workflow or outcome. The numbers they report then describe whichever workflows happened to finish last, not the CI pipeline.

Evidence

Sweep run 20261004T190412Z (2026-10-04 ~19:05Z):

  • The cited reproduce runs include 37226835052, a maintenance-audit-test-selection run triggered by workflow_run (jobs audit-failed-suite-selection, audit-test-selection), plus ci.yml runs 37226761806, 37226760077 and 37226759351, each a ~30 s failure.
  • The report states "CI run length median 0.48 ci-minutes" and "slowest CI step Fetch base in job scope, median 9000 ms (3 samples)".
  • The most recent successful ci.yml run in the same window, 37224898651, took about 4 min 19 s (18:33:34Z to 18:37:53Z). The 0.48-minute median comes from fast failures and a maintenance workflow, so it understates CI length roughly ninefold.

Fix

  • Sample per workflow (at minimum the required-check workflow, ci.yml here), and report each separately.
  • Separate successful full runs from failed and skipped ones: a fast failure is not a short CI run.
  • Name the workflow and outcome beside every CI number in the report.
  • A test with a mixed run list that expects per-workflow, success-only medians.
Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
7 h 8 min
PR fusionados (30 d)
874

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 melodic-software/claude-code-plugins

Todos los issues de melodic-software/claude-code-plugins

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.