Closed Bug 734327 Opened 13 years ago Closed 13 years ago

master_cleanup not working properly on preproduction-master

Categories

(Release Engineering :: General, defect, P2)

Product:
Release Engineering
Component:
General
Platform:
x86
Linux
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nthomas, Assigned: rail)

Details

[87] preproduction-master.build.sjc1:disk - /builds is WARNING: DISK WARNING - free space: /builds 3059 MB (10% inode=26%): leads to the discovery that /builds/buildbot/builder_master is about 21G. A lot of that is in the *-l10n-nighlty dirs (1-2G each), and there are files in there going back to last September. AIUI the cron job calls to master_cleanup.py should be keeping this under control, but something isn't working right. Those try/except blocks with continues look like good places to start. I've killed anything older than 10 days in mozilla-central-linux-l10n-nightly to get a rest from the nagios alerts. Rail, could you take a look ?
Actually the script was OK, but it doesn't clean old builder files. I added a couple of commands to the weekly master-setup builder to cleanup master directory. /dev/sdb1 30G 3.9G 25G 14% /builds
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.