cleanup_disk not built for all supported platforms |
|||
Issue descriptionI've verified this on most of the bots powering http://build.chromium.org/p/chromium.perf/builders/Mac%20Builder I've done some debugging with friedman@, and we can't find anything very suspicious.
,
Nov 10 2017
Apparently darwin doesn't report arch as amd64 or i386... x86-64 and x86 only. Ugh. I'll fix this for now but we should really just build this package for all platforms now that cipd supports them all. I'll reassign when fixed.
,
Nov 10 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/infra/puppet/+/5b5ae0f21dba90f8238bca07ee8ccb53dda1c1bd commit 5b5ae0f21dba90f8238bca07ee8ccb53dda1c1bd Author: Elliott Friedman <friedman@google.com> Date: Fri Nov 10 20:23:33 2017
,
Nov 10 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/infra/puppet/+/389150c0b1b1a398a2a4083c2b801fe44c29b53a commit 389150c0b1b1a398a2a4083c2b801fe44c29b53a Author: Elliott Friedman <friedman@google.com> Date: Fri Nov 10 20:33:43 2017
,
Nov 10 2017
Notice: /Stage[main]/Chrome_infra::Setup::Cleanup_disk/Cron[cleanup_disk]/ensure: created Notice: Finished catalog run in 13.44 seconds [2] chrome-bot@vm171-m1:(Mac 10.12.5):~ $ crontab -l # HEADER: This file was autogenerated at 2017-11-10 12:34:30 -0800 by puppet. # HEADER: While it can still be managed manually, it is definitely not recommended. # HEADER: Note particularly that the comments starting with 'Puppet Name' should # HEADER: not be deleted, as doing so could cause duplicate cron jobs. # Puppet Name: cleanup_disk 35 0 * * * /usr/bin/nice -n 20 /opt/infra-tools/cleanup_disk > /dev/null 2>&1
,
Jun 8 2018
I ssh-ed onto a bot and it has cleanup_disk. I think this can be closed? |
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Nov 10 2017