Chris Maddock

I believe issue 1 is a duplicate of https://github.com/nunit/nunit/issues/1381 (Although an excellent bug report for it - much appreciated!) This one, I agree is a clear cut bug which should...

Just to be completely clear, I would propose the following: - If `--explore` encounters an exception, is should show that exception the same as it would if it was encountered...

Because that only (currently) exists under the `--trace=xxx` option. It would also require an amount of additional processing, to work out which part of the log to present to the...

> It wouldn't work when/if we ever get agents running on additional machines Fair. I imagine multiple agents on a single machine will remain the main usage however, which would...

Plans to take this further now up for discussion in #948

@vinaychandra Can I ask what the motivation for this is? I would have thought the main purpose of timeout is to kill particularly tests which may be flaky/unreliable. That doesn't...

> In fact, my experimentation with pluggable agents showed me that the agent needs to know what runtimes it can run on., so making this an agent responsibility is sensible....

If this remains the case in the latest version of the engine, let's remove the count attribute from start-run in v4. It's inaccurate, and there's no clear efficient solution to...

Sounds good. I assumed that it had never worked so nobody could be relying on it, but sounds like that's not the case.

For v4.0, I think we just remove the attribute as the minimal change for correctness. The feature has never worked, so feels more like we're adding a new feature -...