is-alive and stop methods strange behavior

[Ladas]

It seems like is-alive gives return code 0 while the job is running and 1 once it's done. Is that the expected behavior?

But stop gives always return code 1, there is no error (even if I use -vvvvv or --debug), and the process keeps running. But after a current play finishes, it seems to stop (output file is blank and rc is missing). Is waiting till the current play finishes? It would be good to fill in the rc at least.

If stop is a graceful exit, could we add also kill method?

[Ladas]

ping @matburt

[matburt]

I think something is totally borked with start / is-alive / stop.

I'll take a look

[chessbyte]

@matburt was this ever addressed?