Add additional logging for spawnFromEvent

Currently when adb fails, we skip the error and it is hard to understand that it has failed.
In fact adb writes to stderr in some cases. In order to debug such cases (until we implement proper parsing), add additional logging for the spawnFromEvent method.

Author: rosen-vladimirov

child-process.ts

@@ -84,6 +84,8 @@ export class ChildProcess implements IChildProcess {
 
 			if(spawnFromEventOptions && spawnFromEventOptions.throwError === false) {
 				if(!future.isResolved()) {
+					this.$logger.trace("Result when throw error is false:");
+					this.$logger.trace(result);
 					future.return(result);
 				}
 			} else {

mobile/android/android-debug-bridge.ts

@@ -16,6 +16,8 @@ export class AndroidDebugBridge implements Mobile.IAndroidDebugBridge {
 	public executeCommand(args: string[]): IFuture<any> {
 		return (() => {
 			let command = this.composeCommand(args).wait();
+			// TODO: Remove throwError when adb output parse is implemented.
+			// For example `adb -s <invalid device id> install <smth>` throws error 'error: device \'030939f508e6c773\' not found\r\n' exitCode 4294967295
 			return this.$childProcess.spawnFromEvent(command.command, command.args, "close", undefined, {throwError: false}).wait().stdout;
 		}).future<any>()();
 	}