Say where a stuck comparison is stuck (diagnostics) #176
Loading…
Reference in a new issue
No description provided.
Delete branch "diagnose-stuck-compare"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What #175's lines showed
The live app measures no standby because comparisons pile up behind one that never ends:
Read from the container at 03:00, read only:
ffmpegwas running.One comparison runs at a time, so one that never ends stops every one after it. That is how every pair stayed "pending" after #172's deploy: the few comparisons that finished first were too few to reach "No match".
Before it stuck the measuring worked. Two pairs were found, and a recovery at 02:47:26 on Stars vs. Panthers was the first aimed change of stream live: it moved the picture −0.1 s, by the timestamps.
What this adds (logging only)
Checks
make test: 1,485 passed, 1 skipped. The new test holds a comparison in its search and checks three things: the report says what it was doing, it names the busy thread's stack, and the comparison is no longer listed once it ends.🤖 Generated with Claude Code