faft: Disable stdout buffering of remote FAFTClient
When the remote FAFTClient fails to serve, FAFT dumps its log file for debug.
However, we found that most of the log is buffered and not show in the log
file. We should disable the stdout buffering of FAFTClient.
We also enable the logRequests of SimpleXMLRPCServer for debug.
BUG=None
TEST=run a FAFT test and cat the remote /tmp/faft_client.log, see complete log:
Executing crossystem fwid
ti | lm4fs1gh5bb | link_v1.2.107-5c59877
Executing rootdev -s
Executing rootdev -s
Executing cgpt show /dev/sda
Executing dd if=/dev/sda2 of=/var/tmp/faft/part.tmp bs=1 count=16384
Executing dd if=/dev/sda2 of=/var/tmp/faft/part.tmp bs=1 count=16384
Executing dd if=/dev/sda4 of=/var/tmp/faft/part.tmp bs=1 count=16384
Executing dd if=/dev/sda4 of=/var/tmp/faft/part.tmp bs=1 count=16384
Executing initctl status tcsd
Executing tpmc read 0x1008 0xd
Executing tpmc read 0x1007 0xa
Requesting get root device
Executing rootdev -s
XMLRPC Server: Serving FAFTClient on port 9990
localhost - - [31/Oct/2012 22:54:00] "POST /RPC2 HTTP/1.0" 200 -
Requesting get platform name
Executing mosys platform name
...
Change-Id: Ic3ecfcc9ee872c5db2bf7d5bfe794ce3721b2ead
Reviewed-on: https://gerrit.chromium.org/gerrit/37108
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>
2 files changed