Closed Bug 433756 Opened 15 years ago Closed 15 years ago

mozilla-central build-on-landing builds are all clobbers


(Release Engineering :: General, defect, P1)



(Not tracked)



(Reporter: dbaron, Assigned: bhearsum)




(1 file)

So, looking at the logs of the mozilla-central non-talos tinderboxes, it seems like any build that resulted from a checkin (i.e., a build-on-landing build rather than the 2 hour timeout) does a clobber.  This seems broken, and will slow down tinderbox cycle times a good bit.

I'm seeing this on mozilla-central-linux, mozilla-central-linux-debug, etc.

Compare the logs, for example, from today's 11:46:11 build (exactly 2 hours after the 9:46 build) with today's 12:00:59 builds (resulting from my checkin of bug 433708).

The 11:46:11 builds begin with:

removed `obj-firefox/dist/firefox-3.1a1pre.en-US.linux-i686.tar.bz2'
pulling from
real URL is
searching for changes
no changes found

whereas the 12:00:59 builds begin with:

removed `obj-firefox/dist/firefox-3.1a1pre.en-US.linux-i686.tar.bz2'
real URL is
requesting all changes
adding changesets
adding manifests
adding file changes
added 15124 changesets with 82098 changes to 34522 files
31407 files updated, 0 files merged, 0 files removed, 0 files unresolved

... and then proceed to repull all of NSPR, NSS, etc.

I'm seeing this on mozilla-central-linux, mozilla-central-win32-debug, etc.
I'll have a look at this tomorrow.
Assignee: nobody → bhearsum
Looks like this is a Buildbot bug. I'm working on a patch.
This patch worked fine in a local test. I'm going to test it on staging now.
This patch totally fixed the issue. I'll get this checked in and deployed ASAP.

Upstream patch is here:
Priority: -- → P1
Attachment #321066 - Flags: review?(rcampbell)
Attachment #321066 - Flags: review?(rcampbell) → review+
Comment on attachment 321066 [details] [diff] [review]
[checked in] fix Mercurial Source class

Checking in buildbot/slave/;
/cvsroot/mozilla/tools/buildbot/buildbot/slave/,v  <--
new revision: 1.4; previous revision: 1.3
Attachment #321066 - Attachment description: potential patch → [checked in] fix Mercurial Source class
I've deployed on a couple of slaves, waiting for builds on the others' to finish before I can deploy on the rest of them.
Alright, it's been deployed everywhere - this is fixed.
Closed: 15 years ago
Resolution: --- → FIXED
Product: → Release Engineering
You need to log in before you can comment on or make changes to this bug.