together with Anna Stępień and Maciej Biłas we started working on following issues:
We decided to focus on handling CTRL-C during test execution in sbt console.
As for now we:
But then incidentally we found Signal (in util/collection/src/main/scala/sbt) and TaskCancellationStrategy.Signal that was introduced by:
Author: Josh Suereth firstname.lastname@example.org
Date: Mon Apr 7 16:42:08 2014 -0400
Part #1 of cancel-task-hooks - Hooks EvaluateTask.
a year ago. And we found that after setting
set cancelable in Global := true CTRL-C interrupts threads related to the task that's being executed.
Our idea was CTRL-C should stop executing new test cases and then (e.g. after second CTRL-C/some timeout) interrupt TestingFramework threads because interrupting threads is quite
dirty in our opinion.
But maybe interrupting threads is the right thing to do - it's dirty but it's also simple and works for all kind of tasks, not only for
What do you think is a better strategy? Is it provi