Cancel running checks and report what did not run
Pressing Ctrl+C stops the runner but leaves a test child consuming CPU. Add cancellation with a bounded grace period and explicit cancelled outcomes.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Process lifecycle · Cross-platform tooling · Cancellation
Estimated field mix
- Developer tooling100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A product team waits for every package to rebuild after small changes. An experimental cache is faster but occasionally returns success after a shared type changed. Build a small, auditable task runner around fixture packages.
Setup prerequisites
- Prepare four fixture packages with one shared library and two applications.
- Use only trusted fixture commands in local tests.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Cancellation stops new starts immediately and requests termination of every owned process tree.
- After the configured grace period remaining owned processes are forcefully terminated using supported platform behavior.
- The summary distinguishes failed, cancelled, blocked, and completed tasks and returns a nonzero exit.
Implementation constraints
- Exercise only controlled fixture child processes.
- Do not terminate processes outside the operation ownership set.
Verification to include
- Cancel a parent fixture that owns a long-lived child and confirm both are gone.
- Cancel while one independent task has completed and verify its successful result remains in the summary.
Deliverables
- Cancellation handler and process-cleanup test
Rollout and recovery
Enable cancellation together with process ownership tracking; retain the serial execution fallback if cleanup fails on a supported OS.
Value of the work
For the engineer: Practice incremental computation, dependency scheduling, cache correctness, and cancellation.
For the team: Inspect whether faster checks preserve the guarantees reviewers depend on.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.