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

[FEATURE REQUEST] Scripts to make updating ref images easy

Abierto
  • ¿Algo no está bien?
#2,182 4 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
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
cpp, github-actions
Área
computer-graphics, testing

Línea de trabajo

Start by reviewing the CI workflow and its failed-test artifacts, then locate the tests’ ref/ directories and how reference-image comparisons are handled. The request is exploratory and does not identify specific files or a chosen implementation; first clarify whether this should be a script, agent skill, or agent-assisted tool. Done means automating artifact collection and reference-image updates while showing proposed image changes for human approval.

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

Descripción

build / testing / port / CI

(Summarize discussion that happened at the TSC meeting)

Sometimes you make a change that might alter output images, and CI jobs fail.

If it's just one or two jobs, and they fail on the same test or two, usually it's just a matter of downloading the "failed test" artifacts from that job, unzipping it locally, checking the image visually, and if it looks correct, copying it to the ref/ subdirectory of that test, an pushing the amendment.

But sometimes it's a whole bunch of tests, or different tests fail for different jobs in the CI workflow, or they produced different changes per platform and need multiple reference tests. Then it gets really tedious.

So we fantasized that something that automates the following would be really helpful:

  • Figure out which jobs / configurations failed across the CI workflow, download all the relevant artifacts.
  • Figure out if each test failed in the same way across all the job variants (replace one ref image?), or in different ways (maybe it needs multiple ref images, or needs a wider comparison threshold?).
  • Sort it all out and replace or add ref images.
  • VISUALLY show the human all the before/after images of the proposed changes, either interactively, or as a web page, get confirmation that a "bad image" isn't sneaking in.
  • Commit the changes.

Maybe it's an agent skill? Maybe it's just just using agents to write the complicated script that does the above, which we've all been too lazy to do ourselves?

Lenguaje dominante
C++
Estrellas
2.3k
Forks
414
Merge medio
4 d 2 h
PR fusionados (30 d)
19

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 AcademySoftwareFoundation/OpenShadingLanguage

Todos los issues de AcademySoftwareFoundation/OpenShadingLanguage

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.