https://build.chromium.org/p/chromium.fyi/builders/Chromium%20Mac%2010.9%20Goma%20Canary%20%28dbg%29%28clobber%29/builds/34595/steps/steps/logs/stdio

ERROR:remote_run:Buildslave disk is full! Please contact the trooper.

The disk is scribbled so I am redeploying it.

Re:#2  Redeploying the slave for Chromium Mac 10.9 Goma Canary (dbg)(clobber)

btw, this is supposed to be running 10.9?   The slave was running 10.12.  

The root cause is still issue 775142, and the fact that you are re-imaging this machine is yet another proof of issue 775142 is wasting chrome-ops team huge amount of time.

vm657-m1 ( Chromium Mac 10.9 Goma Canary ) has it's keychain directory that needs purging?

chrome-bot@vm657-m1:(Mac 10.12.2):/Library$ du -sh Keychains/
 36G	Keychains/

Just did a rm /Library/Keychains/apsd.keychain.sb-*

vm658-m1 (Chromium Mac 10.9 Goma Canary (dbg)):

This slave has a build directory that is no longer in use?:
chrome-bot@vm658-m1:(Mac 10.12.2):/b/c/builder$ du -sh  *
 63G	Chromium_Mac_10_9_Goma_Canary__dbg_
 91G	mac

Removed Chromium_Mac_10_9_Goma_Canary__dbg_

vm912-m1 Chromium Linux Goma Canary, rm'd the unused build directory:
/b/c/builder/Chromium_Linux_Goma_Canary

chrome-bot@vm912-m1:(Linux 14.04):/b/c$ du -sh *

still Chromium Linux Goma Canary failing?
https://build.chromium.org/p/chromium.fyi/builders/Chromium%20Linux%20Goma%20Canary/builds/141559

/b/c/chrome_staging is huge.

$ du -hs chrome_staging/
127G   chrome_staging/

removing full-build-linux* in this dir.
$ rm -fe chrome_staging/full-build-linux*
$ du -hs chrome_staging/
8.0K   chrome_staging/

/b/c$ df -h .
FIlesystem    Size  Used Avail Use%  Mounted on
/dev/sdb1     246G  101G  134G  43%  /mnt/data

passed: https://build.chromium.org/p/chromium.fyi/builders/Chromium%20Linux%20Goma%20Canary/builds/141563

Chromium Linux Goma Canary fails again with disk full.

Nov 22 00:32	d44c932dd455b5f12346dfdb2ab60a56a34c442d	exception	#141586
Exception steps exception package build failed failure reason
Nov 21 23:30	43644430175628bf838aae733530e25f96bf40c0	exception	#141585
Exception steps exception package build failed failure reason
Nov 21 22:20	d0c8e462bf029f31a7b9648ac2a5a4a54287d0cd	success	#141584
Build successful
Nov 21 20:56	2a3ed890df45df9e109d935f5448ca60e4f2ac55	success	#141583
Build successful
Nov 21 19:54	10533cf121c9c5b969921aacc91d52270c3e3430	success	#141582
Build successful
Nov 21 18:54	ee41ffee3151b23dfe5a9e25b2ffe0d8a255b6a1	success	#141581
Build successful
Nov 21 17:55	e1ea6b1bb320eb9cd9b7d10e70e0a5d69ae9977b	success	#141580
Build successful
Nov 21 16:51	d2d6ee9c44327d3f4518dbc904f8c7d4aa4128af	success	#141579
Build successful
Nov 21 15:43	75ef3e360ead4ff096fc11722d5950d53518c34a	success	#141578
Build successful
Nov 21 14:41	e9d9276f01cc151c9718ec82cd5ee8ff7f07fde2	success	#141577
Build successful
Nov 21 13:42	00fecee965380f9c1b8043f500fdffef9f854890	success	#141576
Build successful
Nov 21 12:33	86c8199e89e3991732f8375fad1f1b667cc7edf4	success	#141575
Build successful
Nov 21 11:34	08b0819307cc7d1a973e7d938ff156527519c791	success	#141574
Build successful
Nov 21 10:29	28d2ab7b1d50205d0fd6313b84e3b6b8f9d657c3	success	#141573
Build successful
Nov 21 09:10	4ca16519443184833fe0653ed552de88156dc6fa	success	#141572
Build successful
Nov 21 07:57	6d91436f8016aa3bcaa6953b452f967bce50406a	success	#141571
Build successful
Nov 21 06:56	9d2bc3eaf729a97bab085062151676e5e8a374a3	success	#141570
Build successful
Nov 21 05:55	7a3927423e4acafd32f5d480c6a04cc4a940a48f	success	#141569
Build successful
Nov 21 04:43	4e14dc3f46a0e9f50c88f58b2ef607885342f9e8	success	#141568
Build successful
Nov 21 03:41	1f354350d8591ef0904b1084ffd1625e3878ae0d	success	#141567
Build successful
Nov 21 02:00	f4c312133cc23628484d67ce590320a5aab7ac3c	success	#141566
Build successful
Nov 21 01:00	264ffbd68fbac550b9d953b4a793aa7db9bb5d92	success	#141565
Build successful
Nov 20 23:56	e0b80f1df63e1864fbcb938add6525c2ce7393f1	success	#141564
Build successful
Nov 20 22:54	4252b6f6e11eca63f0ee895744566d19f09ba102	success	#141563
Build successful
Nov 20 22:14	fbbf434ba94f5e150b0dfc1b830f7829f0e4e177	exception	#141562
Exception steps exception package build failed failure reason
Nov 20 21:33	0d16ca1cf9089047493f2e1abbe1c30b3b619aa1	exception	#141561
Exception steps exception package build failed failure reason

removed full-build-linux*.zip in /b/c/chrome_staging again.
why does it exist?

disk is small for prune_limit=3 ?

https://chromium.googlesource.com/chromium/tools/build/+/master/scripts/slave/zip_build.py#430

full-build-linux dir is 68G
with full-build-linux dir and without *.zip in /b/c/chrome_staging, disk available only 42G now (193G used)

chrome-bot@vm912-m1:(Linux 14.04):/b/c$ du -hs *
89G     builder
68G     chrome_staging
34M     cipd
14G     git
83M     goma
61M     goma_cache
114M    goma_client
232M    vpython
chrome-bot@vm912-m1:(Linux 14.04):/b/c$ ls chrome_staging/
full-build-linux  FULL_BUILD_REVISION
chrome-bot@vm912-m1:(Linux 14.04):/b/c$ ls builder
linux
chrome-bot@vm912-m1:(Linux 14.04):/b/c$ ls builder/linux
full_results.json  src  times_ms.json

seems try server uses 492G.

could you increase disk size of Chromium Linux Goma Canary vm912-m1?

ping

ping again

Done.  Effective starting with https://build.chromium.org/p/chromium.linux/builders/Fuchsia%20x64%20Cast%20Audio/builds/247

I think that builder link isn't the one you intended. That said, the last two builds here https://build.chromium.org/p/chromium.fyi/builders/Chromium%20Linux%20Goma%20Canary/ have succeeded.

Thanks for catching that, wrong tab.