Closed
Bug 649262
Opened 13 years ago
Closed 13 years ago
TraceMonkey Linux opt broken in purge_builds.py
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philor, Assigned: catlee)
Details
Attachments
(1 file, 1 obsolete file)
2.19 KB,
patch
|
lsblakk
:
review+
lsblakk
:
checked-in+
|
Details | Diff | Splinter Review |
Since around noon Monday: http://tinderbox.mozilla.org/showlog.cgi?log=TraceMonkey/1302590733.1302590951.25012.gz set props: purge_target === Output === python tools/buildfarm/maintenance/purge_builds.py -s "{'build_space': 7}" -n info -n 'rel-*' .. /scratchbox/users/cltbld/home/cltbld/build in dir /builds/moz2_slave/tm-lnx/. (timeout 3600 secs) watching logfiles {} argv: ['python', 'tools/buildfarm/maintenance/purge_builds.py', '-s', "{'build_space': 7}", '-n', 'info', '-n', 'rel-*', '..', '/scratchbox/users/cltbld/home/cltbld/build'] ... using PTY: True Usage: Delete old buildbot builds to make room for the current build. purge_builds.py [options] base_dir1 [base_dir2 ...] base_dir1 is the root of the directory tree you want to delete builds from. Sub-directories of base_dir1 will be deleted, in order from oldest to newest, until the specified amount of space is free. base_dir1 will always be used for space calculations, but if other base_dir# are provided, subdirectories within those dirs will also be purged. This will obviously only increase the available space if the other base_dirs are on the same mountpoint, but this can be useful for, e.g., cleaning up scratchbox. example: python purge_builds.py -s 6 /builds/moz2_slave /scratchbox/users/cltbld/home/cltbld/build purge_builds.py: error: option -s: invalid floating-point value: "{'build_space': 7}" program finished with exit code 2 elapsedTime=0.062805 purge_target: "{'build_space': 7}GB"
Assignee | ||
Comment 1•13 years ago
|
||
Attachment #525362 -
Flags: review?(lsblakk)
Assignee | ||
Comment 2•13 years ago
|
||
Attachment #525362 -
Attachment is obsolete: true
Attachment #525362 -
Flags: review?(lsblakk)
Attachment #525363 -
Flags: review?(lsblakk)
Comment 3•13 years ago
|
||
Comment on attachment 525363 [details] [diff] [review] Fix project branches > >+ if branch in PROJECT_BRANCHES and 'platforms' in PROJECT_BRANCHES[branch] and \ >+ PROJECT_BRANCHES[branch]['platforms'].has_key(platform): >+ for key, value in PROJECT_BRANCHES[branch]['platforms'][platform].items(): >+ BRANCHES[branch]['platforms'][platform][key] = deepcopy(value) >+ >+ if branch in ACTIVE_PROJECT_BRANCHES is what I'd do here just to save time on any (eventual) branches that aren't turned on for some reason. r+ with that
Attachment #525363 -
Flags: review?(lsblakk) → review+
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → catlee
Comment 4•13 years ago
|
||
Comment on attachment 525363 [details] [diff] [review] Fix project branches http://hg.mozilla.org/build/buildbot-configs/rev/27150df8225b
Attachment #525363 -
Flags: checked-in+
Comment 5•13 years ago
|
||
This has landed in production.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•