Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
  • Is something wrong?
#6,621 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
shell
Domain
testing-qa, tooling

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Shell
Stars
22
Forks
2
Avg merge
5h 15m
Merged PRs (30d)
833

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from melodic-software/claude-code-plugins

All issues in melodic-software/claude-code-plugins

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.