We currently allow one to run a command synchronously by calling |host_object.run("command")|. There exists a framework for spawning, keeping track of, and killing background jobs in client/common_lib/base_utils.py (search for BgJob, and look at the usage in |run()|). It would be nice if we could leverage the same infrastructure to allow commands to be spawned in the background, and to later check to see if they're completed, what the exit code was, and what the command's output was.

Moved to: Issue chromium:221930