Closed Bug 989579 Opened 12 years ago Closed 9 years ago

hgtool clobbering should lead to a TinderboxPrint message

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: glandium, Unassigned)

Details

Currently, clobberer-triggered clobbers, and build-system-triggered clobbers are easily visible from tbpl, through a TinderboxPrint message. But there's another class of clobbers that aren't visible: when hgtool clobbers for some reason. See http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-win32/1396054769/mozilla-inbound-win32-bm82-build1-build1706.txt.gz for example, which, in fact, was likely that a previous clobber clobbered the source tree. So in fact, maybe we should distinguish between "had nothing there" and "hgtool clobbered it for some reason".
we don't generally use hgtool now that we have robustclone.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.