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

fix(testing): test-judge gives up when the judge exits 0 with no usable result, and re-logs deleted files on every Stop

Chiusa
  • Qualcosa non va?
#6,621 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Una pull request collegata è già stata integrata.

  • #7091 di @kyle-sexton — integrata

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
55/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
shell
Ambito
testing-qa, tooling

Direzione di ricerca

Start by locating the test-judge Stop hook and the session-state handling that records edited files; the issue does not name specific files or tests. Reproduce both cases: a judge exits successfully without a usable result, and a tracked file is missing on Stop. Done means failed attempts retain raw output or an excerpt, any verified comma-truncation is fixed, and a missing file is dropped after its first skip.

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

Descrizione

needs-triage priority: medium

Two test-judge problems on Windows (melo-desk-001, 2026-10-06 and 2026-10-07), seen in ~/.claude/plugins/data/testing-melodic-software/test-judge.log.

1. The judge exits 0 with no usable result

The Stop hook reported: test judge: 1 test not judged after 2 failed attempts. The log shows:

2026-10-07T22:46:11Z attempt failed: 0614dba8d46a0f02a22340109b2f4f57: judge exited 0 with no usable result
2026-10-07T22:46:11Z not judged, the judge failed for: Provisioning.Tests.ps1: stops the leader and exits when its parent, the task
2026-10-07T22:46:39Z attempt failed: 0614dba8d46a0f02a22340109b2f4f57: judge exited 0 with no usable result
2026-10-07T22:46:40Z judge not run after 2 failed attempts for: Provisioning.Tests.ps1: stops the leader and exits when its parent, the task

The log has 12 no usable result lines over two days: 5 on 10-06 and 7 on 10-07. The judge's raw output is not kept, so the cause can't be determined from the log. In the logged test name, a Pester It description from melodic-software/provisioning, the name ends at a comma (...its parent, the task). That may be truncation of a name containing a comma, or only how the log line is written. This is not verified.

Expected:

  • keep the judge's raw output, or an excerpt, for any attempt that produces no usable result, so the failure can be diagnosed
  • if the test-name extraction cuts at a comma, fix it

2. Files deleted from the session are re-logged on every Stop

A file the session edited lives in a worktree that was later removed. After that, every Stop logs skipped: <path> no longer exists again for the same set of files. The current log has 2,257 such lines, and the same 11 paths repeat at 22:18, 22:20 and 22:46. pending/ is empty, so the entries come from session state, not the queue.

Expected: drop a missing file from the session's set once, on the first skip, so it is not re-checked or re-logged on later Stops.

Found during the 2026-10-07 C: disk incident cleanup, where many worktrees were removed after their PRs merged.

Lingua principale
Shell
Stelle
22
Fork
2
Merge medio
8h 41m
PR unite (30g)
892

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

Tutte le issue di melodic-software/claude-code-plugins

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.