fix(scheduler): break jobid= filters accept every jobid form the REPL prints (bug-1926)
repl_u64_str_eq() compared the packed jobid's raw decimal string with the filter text, so a breakpoint on the dashed jobid the REPL prints never fired. The filter is now parsed once when the breakpoint is set (repl_parse_jobsel_arg, moved to repl_fmt.c) and matched with repl_jobsel_matches: dashed ids, X[k], X[a-b] and raw decimal ids all work, a bare array-aligned id also matches its elements, and an unparseable value is rejected instead of creating a dead breakpoint. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
d2a94ebc3e
commit
7aef6b85c9
6 changed files with 501 additions and 69 deletions
|
|
@ -26,8 +26,8 @@
|
|||
* (0-0-0-32768[1] and [2]) and a host-selection mismatch (203 selects
|
||||
* mem>20000, which only w02 has).
|
||||
*
|
||||
* Breakpoint filters compare the raw decimal jobid (repl_break.c
|
||||
* repl_u64_str_eq), so `break DECISION jobid=105` names 0-0-0-105.
|
||||
* `break DECISION jobid=105` (a raw packed decimal id) names 0-0-0-105;
|
||||
* since bug-1926 the dashed form 0-0-0-105 names it too.
|
||||
*
|
||||
* Scenarios:
|
||||
* 1. step mode, all jobs, level full, file copy (baseline replay, five
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue