capture_local to support timeout?

[reasonerjt]

I integrated crashd in my pipeline, when the test case fails this is run to collect some information:

capture_local(cmd=collectionCmd, file_name="collection.log")

Due to a bug in the backend, the case failed and the collectionCmd was blocked until the pipeline timed out and killed the whole process.

It would be friendlier for this scenario if capture_local can accept a new parm timeout so failure is more explicit.

Not sure the change should be made in this repo or gexe. I'm opening the issue here for tracking.

[vladimirvivien]

@reasonerjt this is a good idea.
I think all commands that interact with a resource (compute, local or remote) should support a timeout value.

[klxfeiyang]

@vladimirvivien, bumping this discussion, we would like to utilize the timeout feature as well, because we have observed occasions when crashd would hang for hours collecting logs from specific resources.