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

Benchmark gate: optional valid-task fraction floor, so one flaky lm-eval task does not fail a multi-task run — deferred until a real run reports a flaky-task false failure

Aperta
  • Qualcosa non va?
#914 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
testing

Direzione di ricerca

Start with BenchmarkConfig and run_benchmark, where any invalid lm-eval task score currently fails the whole gate, and with the deferral comment there. Use evaluation.llm_judge.min_valid_fraction as the pattern for an opt-in floor. Done means the floor is off by default, reports excluded tasks, the row at docs/roadmap/risks-and-decisions.md:258 is removed, and the CHANGELOG names the ID. The issue says its trigger is not met, so confirm with a maintainer before starting.

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

Descrizione

area: eval-gates deferred severity: low source: roadmap wave: 4

Deferred work · F-W20260729-CORE-03-floor · severity Low · cost ~2-3 h · recorded in docs/roadmap/risks-and-decisions.md:258

Summary

Phase 16 S2 (decision C-1) made the benchmark gate fail when any lm-eval task returns a non-finite or out-of-range score, so under auto_revert: true one flaky task in a ten-task run deletes the model. A min_valid_fraction-style floor mirroring evaluation.llm_judge.min_valid_fraction was deferred so the strict form's real cost is known before a second threshold is added to a gate that used to pass NaN.

Condition or budget

Revisit if a real run reports a flaky-task false failure. Not met as of 2026-10-09.

State today (re-checked 2026-10-09)

BenchmarkConfig has no valid-fraction field; run_benchmark fails the whole gate on any invalid task score, and its comment records the floor as considered and deferred.

Related

#118 (no "could not evaluate" outcome for infrastructure failures) and #120 (would make missing or no-accuracy tasks fail closed too).

Acceptance criteria

  • An opt-in floor excludes a minority of unusable task scores and reports them, while the default stays strict.
  • The row is removed from the deferral table and the CHANGELOG names its ID (the table's removal contract).

Recorded in docs/roadmap/risks-and-decisions.md (read at f94595f) and re-checked against the code on 2026-10-09. The row leaves that table only when the fix is on main, the CHANGELOG names its ID and any promised guard exists.

Lingua principale
Python
Stelle
9
Fork
1
Merge medio
8h 10m
PR unite (30g)
5

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 HodeTech/ForgeLM

Tutte le issue di HodeTech/ForgeLM

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.