faft: Catch the explicit error when connecting to RPC server
The original catching all exceptions may hide bugs and make us hard to find
the reason of failure. This CL is to catch the explicit errors which are
raised when RPC server does not start fast enough. It also prints the detail
error messages.
BUG=None
TEST=Run a FAFT test and pass.
Change-Id: Iaa007907a195ee414875ebef5f9d8c7827b32f4e
Reviewed-on: https://gerrit.chromium.org/gerrit/37430
Reviewed-by: Vic Yang <victoryang@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
1 file changed