ci-metrics

Consulta métricas de PyTorch CI, GitHub Actions, HUD, Grafana e infraestructura. Úsalo cuando los usuarios pregunten sobre duración de CI, fallos de trabajos, tiempos de cola, tendencias de flujos de trabajo,…

npx skills add https://github.com/pytorch/pytorch --skill ci-metrics

PyTorch CI Metrics

PyTorch CI and infrastructure metrics are exposed through Grafana. Use .claude/skills/ci-metrics/gcx-wrapper.sh for all Grafana access; it configures the PyTorch Grafana server, context, and authentication. Only users with write permission to the repo have access to Grafana. The authentication only provides read only access.

Requirements

The wrapper needs these tools on PATH:

  • gh - fetches the Grafana token and must be authenticated; if not, run gh auth login --hostname github.com --git-protocol ssh --web.
  • curl - downloads gcx and fetches the token from HUD.

On first use the wrapper downloads a pinned, checksum-verified gcx binary into a private cache (~/.cache/pytorch-ci-metrics/) and authenticates automatically. Nothing is installed on your PATH. If a tool is missing or gh is not authenticated, it exits with an error describing what to fix.

Datasources

Get the list of datasources available:

.claude/skills/ci-metrics/gcx-wrapper.sh datasources list

The data contains metrics for many repos owned by the PyTorch repo. When possible, restrict queries to just the pytorch/pytorch repository.

CI and Test Run Data

CI and test run data are stored in grafana-clickhouse-datasource. List all the available tables:

.claude/skills/ci-metrics/gcx-wrapper.sh datasources clickhouse list-tables

Important dataset:

  • GitHub webhook data
  • Tests
    • Database: tests
    • tests.all_test_runs - contains every test run. This is an extremely large table, so be considerate with filtering and timing.
    • Do not use tests.test_run_s3 as it contains partial data only.

To get additional guidance on common queries, clone https://github.com/pytorch/test-infra into a temporary directory and read the torchci folder.

Example Queries

Within the pytorch/pytorch repo on main, list the top most failing workflow jobs in the last 2 weeks:

.claude/skills/ci-metrics/gcx-wrapper.sh datasources clickhouse query "
  SELECT name, count(DISTINCT id) AS failures
  FROM default.workflow_job
  WHERE conclusion = 'failure'
    AND completed_at >= now() - INTERVAL 2 WEEK
    AND repository_full_name = 'pytorch/pytorch'
    AND head_branch = 'main'
  GROUP BY name ORDER BY failures DESC LIMIT 10"

For a test file, how many times was it run in the last week? How many times did it pass or fail?

.claude/skills/ci-metrics/gcx-wrapper.sh datasources clickhouse query "
  SELECT
    file,
    classname,
    name,
    count() AS runs,
    countIf(failure_count = 0 AND error_count = 0 AND skipped_count = 0) AS successful,
    countIf(failure_count > 0 OR error_count > 0) AS fails,
    countIf(skipped_count > 0) AS skipped
  FROM tests.all_test_runs
  WHERE time_inserted >= now() - INTERVAL 7 DAY
    AND file = 'lazy/test_ts_opinfo.py'
  GROUP BY file, classname, name
  ORDER BY runs DESC"

CI Infrastructure

CI infrastructure metrics are stored in grafanacloud-pytorchci-prom. To get a better understanding of the data, clone these repositories in a temporary directory:

Example Queries

Which runner types have the deepest queue right now (jobs assigned but not yet running)?

.claude/skills/ci-metrics/gcx-wrapper.sh datasources prometheus query -d grafanacloud-prom 'topk(10, clamp_min(sum by (name) (gha_assigned_jobs) - sum by (name) (gha_running_jobs), 0))'

How many jobs were running per cluster over the last 6 hours, sampled every 30 minutes? Use --since/--step (or --from/--to) for a range query:

.claude/skills/ci-metrics/gcx-wrapper.sh datasources prometheus query -d grafanacloud-prom 'sum by (cluster) (gha_running_jobs)' --since 6h --step 30m

Más skills de pytorch

zephyr
pytorch
Compila y configura ExecuTorch como un módulo de Zephyr RTOS para placas embebidas. Úsalo al configurar un espacio de trabajo de Zephyr con ET, añadiendo soporte para placas (superposiciones,…
aoti-debug
pytorch
Depurar errores y fallos de AOTInductor (AOTI). Úsalo al encontrar fallos de segmentación de AOTI, errores de discrepancia de dispositivos, fallos en la carga de constantes o errores en tiempo de ejecución de…
skill-writer
pytorch
Guía para crear Skills de Agente bien estructurados para Claude Code con mejores prácticas y validación. Cubre el ciclo de vida completo del Skill: alcance, estructura de archivos, validación de frontmatter YAML, organización de contenido y procedimientos de prueba. Aplica reglas estrictas de nomenclatura (minúsculas, guiones, máximo 64 caracteres) y requisitos de descripción (desencadenantes específicos, tipos de archivo, cláusulas de "qué" y "cuándo"). Proporciona plantillas para patrones comunes, incluyendo Skills de solo lectura, Skills basados en scripts y Skills de múltiples archivos con...
triaging-issues
pytorch
Triage problemas de GitHub asignándolos a equipos de guardia, aplicando etiquetas y cerrando preguntas. Úsalo al procesar nuevos problemas de PyTorch o cuando se te pida triagear un…
wheel-size-analyzer
pytorch
Analiza los tamaños de los wheels nocturnos de PyTorch en un rango de fechas utilizando la API de artefactos de GitHub Actions. Úsalo al rastrear cambios en el tamaño de los binarios, identificar el tamaño de los wheels…
release-go-live-binary-build-matrix
pytorch
Actualiza tools/scripts/generate_binary_build_matrix.py cuando se publique una versión de PyTorch. Avanza CURRENT_STABLE_VERSION a la nueva estable, promueve la…
pr-review
pytorch
Revisa solicitudes de extracción de PyTorch en cuanto a calidad del código, cobertura de pruebas, seguridad y compatibilidad hacia atrás. Úsalo al revisar PRs, cuando se te pida revisar cambios de código,…
qualcomm
pytorch
Construye, prueba o desarrolla el backend de QNN (Qualcomm AI Engine Direct). Úsalo al trabajar en backends/qualcomm/, al compilar QNN (usar…