New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 661724 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jan 2017
Cc:
█ waihong@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

faft leaves numerous log files behind

Project Member Reported by vbendeb@chromium.org, Nov 2 2016 
Each time FAFT server is started on the DUT, the server output console is redirected into a file named /var/log/faft_xmlrpc_server.log.*, each server run uses a different file name.

After running FAFT for a while the /var/log directory accumulates many of these files.

In fact only the last file is of interest, and that mostly in case the test failed.

Starting the server should delete all earlier generated files.

Comment 1 by waihong@chromium.org, Nov 2 2016

Labels: -Pri-2 Pri-3
The * of faft_xmlrpc_server.log.* is the timestamp. Pretty easy to know which one is the last file. One test may generate multiple files (one per DUT reboot). The interested one may not always be the last one.

The file is small, ~1k. The system is regularly reimaged, at least in the lab (reimaged everyday), so will not cause shortage of storage space.

Comment 2 by vbendeb@chromium.org, Nov 2 2016 

FAFT is running not just in the lab, it is worth removing all log files before the next test starts.

Comment 3 by waihong@chromium.org, Nov 2 2016 

Still true in the non-lab case. ChromeBooks usually have multi-GB of disk space. Able to keep quite a lot amount of logs before reimaging.

When running a FAFT suite, having multiple tests, if an user want to check the logs of a failed test in the middle, the logs should better not be removed.

Comment 4 by twreid@chromium.org, Jan 26 2017

Status: WontFix (was: Unconfirmed)
►

Sign in to add a comment