Closed Bug 455934 Opened 17 years ago Closed 17 years ago

mozilla-central leak test needs a clobber

Categories

(Release Engineering :: General, defect, P1)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sdwilsh, Assigned: nthomas)

Details

Linux mozilla-central leak test needs to be clobbered to get rid of nsPlacesDBFlush.js. Not sure if this is a build system bug since the patch that added this has been backed out...
I need more information to act on this. What hosts need to be clobbered?
Assignee: server-ops → aravind
I don't know anything more than it's the second column on the tinderbox page: http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox
It looks like all the unit test boxes are going to need it too - they are going to get the same leak :(
I got to the box from the tinderbox logs on a previous build. I deleted the corresponding build directory, but then the doc says to do something on a waterfall page. I am not sure where that page is. Handing off to build.
Assignee: aravind → nobody
Component: Server Operations: Tinderbox Maintenance → Release Engineering: Maintenance
QA Contact: mrz → release
Aravind says he clobbered on moz2-linux-slave1 so far
Assignee: nobody → nthomas
Priority: -- → P1
Removed objdir/dist/bin on moz2-linux-slave02,03,04,05,06, and forced a build. On to the unit test boxes.
Removed objdir/dist/bin/components/nsPlacesDBFlush.js from qm-centos5-03, qm-centos5-moz2-01 - both while they were testing, so there may be some breakage.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Gah, this isn't limited to linux
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: Linux mozilla-central leak test needs a clobber → mozilla-central leak test needs a clobber
Windows and Mac builders done. On mac, you have to be careful to do <cd objdir> find . -name nsPlacesDBFlush.js -exec rm -v {} \; to get all the copies.
Windows and Mac unit testers also done.
Status: REOPENED → RESOLVED
Closed: 17 years ago17 years ago
Resolution: --- → FIXED
Ah, crap. The two new Windows unit test boxes (moz2-win32-slave07 and 08) have been leaking since about noon on the 18th. 8am-noon was a bunch of failed cycles, and before that they were ok. I'm guessing that these boxes were missed during the previous clobbers, because they were not on the Firefox tinderbox? They are as of today, so they need clobbered.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to comment #11) > Ah, crap. > > The two new Windows unit test boxes (moz2-win32-slave07 and 08) have been > leaking since about noon on the 18th. 8am-noon was a bunch of failed cycles, > and before that they were ok. There was no nsPlacesDBFlush.js in objdir/dist/bin on either. Both clobbered.
Status: REOPENED → RESOLVED
Closed: 17 years ago17 years ago
Resolution: --- → FIXED
I removed the nsPlacesDBFlush.js on bm-xserve16,17,18 (19 didn't have any).
... because the places fsync stuff landed and got backed out again at Wed Oct 08 11:05:08 2008 -0700.
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.