Closed Bug 450506 Opened 16 years ago Closed 16 years ago

need tinderboxs clobbered

Categories

(Release Engineering :: General, defect)

defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Dolske, Unassigned)

References

Details

I'd like to have the trunk tinderboxen clobbered, all platforms. Trying to track down a performance regression in bug 450401. Patches in range have been backed out already to no avail, hoping a clobber will do it. Help me, Obi-Wan Clobberobi; you're my only hope.
What boxes do you need clobbered?
Assignee: server-ops → aravind
Uhm, all of them? In CVS it was just 3 "CLOBBER" files, one each for Windows/OSX/Linux?
I was hoping for explicit hostnames, but I can dig through docs and find that out.
Here are the docs for doing this: https://wiki.mozilla.org/Build:Mac:Moz2:ITSupport#Fixing_Failing_Builds https://wiki.mozilla.org/Build:Win32:Moz2:ITSupport#Fixing_Failing_Builds https://wiki.mozilla.org/Build:Linux:Moz2:ITSupport#Fixing_Failing_Builds Hostnames are: # moz2-linux-slave1 # moz2-linux-slave02 # moz2-linux-slave03 # moz2-linux-slave05 # moz2-linux-slave06 bm-xserve16 bm-xserve17 bm-xserve18 bm-xserve19 moz2-win32-slave1 moz2-win32-slave02 moz2-win32-slave03 moz2-win32-slave05 moz2-win32-slave06
Deleted the build directories on all the linux slaves. Working on xservs next.
Done with the xservs, working on the windows boxes now.
I got almost all of the machines done except moz2-win32-slave06. It seems to be hanging on the directory deletion part. Handing this off to build, since I don't want to go crazy and start deleting random stuff from the box. The rest of them should be done though.
Assignee: aravind → nobody
Component: Server Operations: Tinderbox Maintenance → Release Engineering: Maintenance
QA Contact: mrz → release
slave06 looks good now; build directory all gone.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Component: Release Engineering: Maintenance → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.