[Swan-dev] should final.sh shut down pluto?

[Andrew Cagney]

On 24 June 2016 at 11:43, Antony Antony <antony at phenome.org> wrote:
>
>> - after final.sh has been run, there should be a better defined tear
>> down / extract step to kill off pluto and then extract its logs (I
>> suspect this fits in better with docker).
>
> It is important not to shutdown when you want to manually debug single test.
>
> The current setup is easier to leave the host running and manually login debug further.
> I have a bias to keep doing this. Also currently when runng with TESTLIST it is alway shutdown.
> What is missing in this model?

This lacks consistency, the test results should be the same whether
the test is run individually or as part of a batch.

Orthogonal to this is a way to stop a test at a particular point.  For instance:

- the bit rotten runkvm.py tried to do this with options such as
--testname and --final
- kvmunner.py leaves the domains running with the last test (after
gathering results)

I kind of like something along the lines of runkvm's -- run everything
up to and including a given script.

As my original post tried to point out, if pluto crashes (not aborts)
while the machine is shutting down we'll miss that - I just happened
to notice the problem because I had an inconsistency between some
counters.