test(maestro-case): harden checkers and a few tests - #2560
Conversation
|
Claude finished @charlesliu9's task in 2m 16s —— View job Coder-eval task lint (advisory)
Coder-eval task lint (advisory)1 task YAML changed; 0 Critical, 0 High, 0 Medium, 0 Low, 1 OK. Rubric: .claude/commands/lint-task.md. This check is advisory and never blocks merge. Evidence of passing run❌ High — PR body does not claim the modified task has been run and still passes. Please edit the PR description to add a line like: Per-task lint
|
|
Claude finished @charlesliu9's task in 2m 36s —— View job PR Review: test(maestro-case): harden checkers and a few tests
SummaryHardens the Change-by-Change Review1.
|
| Area | Status | Notes |
|---|---|---|
| Frontmatter | N/A | No skill SKILL.md changed |
| E2E Tests | OK | Both checker changes covered by unit tests |
| Skill Body | N/A | No skill body changed |
| References & Assets | N/A | No references or assets changed |
| Repo Hygiene | OK | No secrets, no cross-skill deps, changes scoped to maestro-case test infra |
Issues for Manual Review
None found.
Conclusion
Clean PR. The timeout handler is well-structured — catches the right exception, decodes bytes defensively, and surfaces partial output for debugging. The regex loosening is minimal and precisely targeted. The new tests exercise the exact edge cases motivating the changes. No issues to flag — approve.
|
test(maestro-case): harden checkers and close the operate-mode coverage gap
Checker robustness:
TimeoutExpired into a FAIL with the partial output, instead of a raw
traceback the eval harness reports as a checker crash. TimeoutExpired
carries bytes even under text=True, so the handler decodes defensively.
without a leading "- " bullet; agents render the contract both ways and
the line-anchored regex was rejecting the plain form.
Both are covered by new unit tests.
Task fixes:
that ProcurementProcess resolves from processOrchestration-index.json,
the recurring cause of a placeholder taskTypeId.