Why is that one so high? Seems unlikely
that anything near 2 G is really needed. Please take following actions
.... or, explain what's up.
a. immediately shrink by removing anything
(e.g. old builds?) that are not absolutely needed.
b. change job configuration settings
or employ some other strategy to keep below 1G on an ongoing basis (or,
again, explain why that can not be done).
c. This job appears to be running on
"master" ... any reason for that? Should be running on slaves.
Let us know if this can not be addressed
by, say, our status meeting on Thursday.
----- Forwarded by David
M Williams/Raleigh/IBM on 02/22/2011 09:10 PM -----
02/22/2011 08:45 PM
Disk usage report for Hudson/Build