[Catapult] Catapult Windows Tryserver: No space left on device |
||||
Issue descriptionTried to land this CL: https://codereview.chromium.org/2693313005 Both times got Catapult Windows Tryserver red: https://build.chromium.org/p/tryserver.client.catapult/builders/Catapult%20Windows%20Tryserver/builds/6418/steps/Tracing%20Python%20Tests/logs/stdio https://build.chromium.org/p/tryserver.client.catapult/builders/Catapult%20Windows%20Tryserver/builds/6422/steps/Dashboard%20Dev%20Server%20Tests%20Stable/logs/stdio With error "IOError: [Errno 28] No space left on device" I have a reason to believe that my CL shouldn't break Windows bot. Could anyone take a look what went wrong with this bot? Thank you!
,
Feb 20 2017
This particular CL has succeded, but worth to take a look anyway.
,
Feb 21 2017
,
Feb 21 2017
Both tryserver slaves are out of space. Investigating. chrome-bot@BUILD78-B1 ~ $ df -hl Filesystem Size Used Avail Use% Mounted on C:/cygwin 239G 239G 7.6M 100% / chrome-bot@BUILD79-B1 ~ $ df -hl Filesystem Size Used Avail Use% Mounted on C:/cygwin 239G 239G 458M 100% /
,
Feb 21 2017
C:\Users\chrome-bot.LABS\AppData\Local\Temp was the culprit. build78-b1: $ df -hl Filesystem Size Used Avail Use% Mounted on C:/cygwin 239G 37G 203G 16% / build79-b1: $ df -hl Filesystem Size Used Avail Use% Mounted on C:/cygwin 239G 37G 203G 16% / |
||||
►
Sign in to add a comment |
||||
Comment 1 by primiano@chromium.org
, Feb 20 2017Components: -Internals>Instrumentation>Memory Infra