Closed
Bug 617920
Opened 14 years ago
Closed 14 years ago
[Windows] Clean Up "No space left on device" (TEMP directories)
Categories
(SeaMonkey :: Release Engineering, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sgautherie, Assigned: Callek)
References
Details
Examples:
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1291879507.1291880165.30085.gz
WINNT 5.2 comm-central-trunk leak test build on 2010/12/08 23:25:07
{
D:\msvs8\VC\INCLUDE\swprintf.inl(112) : fatal error C1088: Cannot flush compiler intermediate file: 'C:/DOCUME~1/seabld/LOCALS~1/Temp\_CL_445b4ef9ex': No space left on device
}
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1291890001.1291892600.30347.gz
WINNT 5.2 comm-central-trunk nightly on 2010/12/09 02:20:01
{
/bin/m4:configure.in:3160: ERROR: cannot flush diversion to temporary file: No space left on device
}
Flags: in-testsuite-
Reporter | ||
Comment 1•14 years ago
|
||
(In reply to comment #0)
s: cn-sea-qm-win2k3-01
***
Test suite failure examples:
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1291863227.1291864332.21784.gz
WINNT 5.2 comm-central-trunk debug test mochitests-1/5 on 2010/12/08 18:53:47
s: cn-sea-qm-win2k3-01
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1291883167.1291884638.17796.gz
WINNT 5.2 comm-central-trunk debug test mochitests-1/5 on 2010/12/09 00:26:07
s: cn-sea-qm-win2k3-01
{
sqlite3.OperationalError: database or disk is full
}
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1291884643.1291885943.24473.gz
WINNT 5.2 comm-central-trunk debug test mochitests-3/5 on 2010/12/09 00:50:43
s: cn-sea-qm-win2k3-01
{
WindowsError: [Error 28] There is not enough space on the disk: 'c:\\docume~1\\seabld\\locals~1\\temp\\tmpmy8ymz'
}
Summary: [Windows] Frequent "No space left on device" since recently → [cn-sea-qm-win2k3-01] Frequent "No space left on device" since recently
Reporter | ||
Comment 2•14 years ago
|
||
major -> blocker, as this causes _many_ test runs to fail:
I guess this box gets selected very often as it "completes" very fast :-<
Severity: major → blocker
Comment 3•14 years ago
|
||
This is a known problem, we are filling up temp directories. Callek, do we have a bug open for that?
Severity: blocker → trivial
Summary: [cn-sea-qm-win2k3-01] Frequent "No space left on device" since recently → [Windows] Frequent "No space left on device" since recently
Whiteboard: [DUPEME]
Assignee | ||
Comment 4•14 years ago
|
||
Probably worth keeping this bug around as reminder to cleanup the machines when they bust. I'll go through all windows ones shortly and clean them again, reopen if it happens again and myself or KaiRo will attack it.
Assignee | ||
Comment 5•14 years ago
|
||
Summary: [Windows] Frequent "No space left on device" since recently → [Windows] Clean Up "No space left on device" (TEMP directories)
Whiteboard: [DUPEME]
Reporter | ||
Comment 6•14 years ago
|
||
Again:
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1294428011.1294430930.28868.gz
WINNT 5.2 comm-central-trunk build on 2011/01/07 11:20:11
cb-seamonkey-win32-01
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → bugspam.Callek
Assignee | ||
Comment 7•14 years ago
|
||
cb-sea-win32-tbox.sj.mozilla.com
cb-seamonkey-win32-01
cb-seamonkey-win32-02
cb-seamonkey-win32-03
all cleaned... only touched seabld's user-space temp; which is the largest. only two machines were completely full; the other two were within KBs of being full.
TODO: fill out a wiki page on "what to do to clean TEMP dirs"
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 8•14 years ago
|
||
Again:
cb-sea-win32-tbox
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Updated•14 years ago
|
Whiteboard: [ETA 2/25/11 ~22:00][cb-sea-win32-tbox taken out of slave pool]
Assignee | ||
Updated•14 years ago
|
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Whiteboard: [ETA 2/25/11 ~22:00][cb-sea-win32-tbox taken out of slave pool]
You need to log in
before you can comment on or make changes to this bug.
Description
•