I think it would be nice to be able to run tests in background. What would be the problem? A test case that fails because you were doing something at the same time? I think it is not so serious, it is up to you to know which tests did you run and do nothing that would conflict with the test run. Now you can't do anything.
On Fri, Sep 16, 2016 at 11:30 AM, Denis Kudriashov <dionisi...@gmail.com> wrote: > > 2016-09-15 18:46 GMT+02:00 Marcus Denker <marcus.den...@inria.fr>: > >> > would itself seem to a big impediment. It would be good if "Author" >> > was dependent on the context of the call chain. This would seem a >> > requirement for one day having two people working in the one Image (is >> > this a possible use case where someone is using a remote debugger >> > while another person is using the standard UI?) >> > >> Could it be part of Denis new ExecutionEnvironment concept? > > > It could be used here but I think such problem is more complex. Most parts > of system is not implemented with concurrency in mind. >
