Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[FEATURE REQUEST] Scripts to make updating ref images easy

Aperta
  • Qualcosa non va?
#2,182 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
cpp, github-actions
Ambito
computer-graphics, testing

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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?

Lingua principale
C++
Stelle
2.3k
Fork
414
Merge medio
4g 2h
PR unite (30g)
16

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di AcademySoftwareFoundation/OpenShadingLanguage

Tutte le issue di AcademySoftwareFoundation/OpenShadingLanguage

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.