cleanup_disk apparently not running everywhere that it ought to |
|||
Issue descriptionb/30718428 showed vm114-m3 as hitting 95% out of disk space on C:\. I manually cleaned it up by deleting C:\Users\chrome-bot\AppData\Local\Temp, but sergey mentioned that this should have been cleaned out automagically by cleanup_disk.
,
Aug 9 2016
[I2016-08-08T00:30:02.414424-07:00 3720 0 cleanup.go:170] Processing C:\Users\chrome-bot\AppData\Local\Temp\* [I2016-08-08T00:30:02.664029-07:00 3720 0 cleanup.go:79] Deleting C:\Users\chrome-bot\AppData\Local\Temp\FXSAPIDebugLogFile.txt [E2016-08-08T00:30:02.664029-07:00 3720 0 cleanup.go:173] Deleting/truncating path failed: C:\Users\chrome-bot\AppData\Local\Temp\* remove C:\Users\chrome-bot\AppData\Local\Temp\FXSAPIDebugLogFile.txt: The process cannot access the file because it is being used by another process. I think it's failing to delete the first file in that directory and exiting immediately. It should continue.
,
Aug 9 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/infra/infra_internal.git/+/54b711e5822f8bf03e194537220a38234b409d1d commit 54b711e5822f8bf03e194537220a38234b409d1d Author: dsansome <dsansome@google.com> Date: Tue Aug 09 07:36:16 2016
,
Aug 9 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by sergeybe...@chromium.org
, Aug 8 2016Status: Available (was: Untriaged)