Closed
Bug 616581
Opened 14 years ago
Closed 14 years ago
'updates' builder didn't clobber correctly for 3.6.13build3
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Unassigned)
References
Details
(Whiteboard: [automation][releases])
I noticed that the updates builder didn't clobber correctly for 3.6.13build3. I dug through the most recent builds for the slave in question and can't figure out why. I set the clobber at 2010-12-03 07:25:14.
Around Fri Dec 3 06:51:21 2010, mv-moz2-linux-ix-slave11 started an android r7 m-c nightly. Its clobberer call showed this for the updates builder:
release-mozilla-1.9.2-updates:Our last clobber date: 2010-11-30 13:45:03
release-mozilla-1.9.2-updates:Server clobber date: 2010-11-30 13:45:03
Around Fri Dec 3 07:29:13 2010, tagging started. Its clobberer call showed this for the updates builder:
release-mozilla-1.9.2-updates:Our last clobber date: 2010-12-03 07:25:14
release-mozilla-1.9.2-updates:Server clobber date: 2010-12-03 07:25:14
Syed, any idea why this would happen? I distinctly remember that clobberer worked in build2, so I'm baffled.
Updated•14 years ago
|
Priority: -- → P2
Whiteboard: [automation][releases]
Reporter | ||
Comment 1•14 years ago
|
||
Fixed by bug 628671.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•