New issue
Advanced search Search tips

Issue 605620 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Slave vm192-m4 seems to run out of disk.

Project Member Reported by st...@chromium.org, Apr 21 2016

Issue description

In https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_variable_gn/builds/32, we got the following error:

[35048/35051] LINK sync_integration_tests.exe
FAILED: E:/b/depot_tools/python276_bin/python.exe gyp-win-tool link-wrapper environment.x64 False link.exe /nologo /OUT:unit_tests.exe /PDB:unit_tests.exe.pdb @unit_tests.exe.rsp
LINK : fatal error LNK1201: error writing to program database 'E:\b\build\slave\win_gn\build\src\out\Debug_x64\unit_tests.exe.pdb'; check for insufficient disk space, invalid path, or insufficient privilege

FAILED: E:/b/depot_tools/python276_bin/python.exe gyp-win-tool link-wrapper environment.x64 False link.exe /nologo /OUT:sync_performance_tests.exe /PDB:sync_performance_tests.exe.pdb @sync_performance_tests.exe.rsp
LINK : warning LNK4081: insufficient disk space; linking nonincrementally

LINK : fatal error LNK1201: error writing to program database 'E:\b\build\slave\win_gn\build\src\out\Debug_x64\sync_performance_tests.exe.pdb'; check for insufficient disk space, invalid path, or insufficient privilege

LINK : warning LNK4081: insufficient disk space; linking nonincrementally

ninja: build stopped: subcommand failed.

E:\b\depot_tools\python276_bin\python.exe E:\b\build\slave\cache\cipd\goma\goma_ctl.py jsonstatus c:\users\chrome~2\appdata\local\temp\tmpnejsa5.json
 

Comment 1 by no...@chromium.org, Apr 21 2016

Owner: no...@chromium.org
Status: Started (was: Untriaged)

Comment 2 by no...@chromium.org, Apr 21 2016

Took this bot offline, will cleanup

Comment 3 by no...@chromium.org, Apr 21 2016

Removed one builder, 74% is free now, continuing investigating what caused it

Comment 4 by no...@chromium.org, Apr 22 2016

Status: Fixed (was: Started)
Didn't find the cause.

Sign in to add a comment