Armen [:armenzg] Reporter
	Description • 16 years ago

Log:
http://staging-master.build.mozilla.org:8010/builders/WINNT%205.2%20mozilla-central%20l10n%20nightly/builds/921/steps/shell/logs/stdio

Build:
http://staging-master.build.mozilla.org:8010/builders/WINNT%205.2%20mozilla-central%20l10n%20nightly/builds/921

	Armen [:armenzg] Reporter
	Comment 1 • 16 years ago

I have logged in, shut off the screen that said "firefox" has crashed (which is probably from the unittest runs)
and removed:
rm -rf tracemonkey-win32*
rm -rf mozilla-central-win32-l10n-nightly

	Armen [:armenzg] Reporter
	Comment 2 • 16 years ago

I cannot remove /e/builds/mozilla-central-win32-l10n-nightly/mozilla-central/dist

Can someone please fix this? I have tried with the Administrator account

Maybe shutting buildbot off and then trying to remove it might work

	Nick Thomas [:nthomas] (UTC+12) Assignee
	Comment 3 • 16 years ago

The root cause is probably the lack of bug 420216, so I'll put that on there. 

As a general comment, if something in a build/test run crashes out then there are usually stray processes left running. After stopping the buildbot slave, there were a python, 2 scp's, about half a dozen ssh's, a link, a ssltunnel, and several make processes still running. I've killed off all of these to get good operation from the slave. Much of this will have built up over time, but it's definitely worth looking in the process list of the task manager and learning what are the normal windows processes and what should be zapped. And this is much less of an issue once we patch twisted so that it can kill things itself, but still worthwhile to know.

	Nick Thomas [:nthomas] (UTC+12) Assignee
	Comment 4 • 16 years ago

Downgraded & patched twisted, removed *-nightly/build/ (17.4GB free), and reconnected to the master.