Panics if error occurs in fastboot parallel tasks
The way we handle errors in fastboot parallel tasks has a few issues:
1. Errors from parallel tasks will make all subsequent commands fail
with the last error, which can be completely unrelated to the current
command and thus confusing.
2. The apporoach requires to track last error inside GblDisk. Both
caller and users need to remember to check the error, which is
error-prone.
3. Users can't do much but to reset the device anyway.
This CL simplifies the handling by just panicing when errors happen and
prints a more informative log message about the failed command and
reason. There is no more need to track last error.
Change-Id: Ifb0fefaeff1a98316a98d5eb41eae90e6cb702bd
7 files changed
