@no-clobber may break process monitoring

[doudou]

I have a cucumber feature file where all the scenarios have @no-clobber, using aruba 0.14.3. This is because the very first feature bootstraps an install and is very expensive. The followup features only use it.

In this file, the steps that involve process management (I should stop, matching on output, ...) do not work (the output is always empty, waiting for process stop always complains that there are no processes started).

I've been putting some strategic puts, and it seems that the process monitor does not get notified of new commands being started. I think that I tracked this down to Setup#call not being called (it's called only in Before("~@no-clobber"), but Setup#events is what links the process monitor to the events.