CLOBBER file should do a full source clobber on unit test machines

RESOLVED INVALID

Status

--
major
RESOLVED INVALID
11 years ago
5 years ago

People

(Reporter: wgianopoulos, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
Checking in changes to the CLOBBER file should result in a full source clobber just like the release build routines do for the nightly, not just an objdir clobber like it does now on depend only build systems.

The fact that it does not caused the tree to be needlessly closed almost all this weekend, because the Windows unit test systems needed a full source clobber to work correctly, and that is what most people thought the CLOBBER file did.
This is just the unit-test boxes right ? The nightly builders remove the source, and objdir if used, when the CLOBBER file is updated.
Component: Build & Release → Testing
Product: mozilla.org → Core
QA Contact: build → testing
Version: other → Trunk
Summary: CLOBBER file should do a full source clobber → CLOBBER file should do a full source clobber on unit test machines
(Reporter)

Comment 2

11 years ago
(In reply to comment #1)
> This is just the unit-test boxes right ? The nightly builders remove the
> source, and objdir if used, when the CLOBBER file is updated.
> 

Yes, unless my proposal in bug 403399 to make it possible to request a clobber on the nightly build boxes without necessarily producing a nightly is accepted.
Mass move of Core:Testing bugs to mozilla.org:ReleaseEngineering. Filter on RelEngMassMove to ignore.
Component: Testing → Release Engineering
Product: Core → mozilla.org
QA Contact: testing → release
Version: Trunk → other
I don't think we have any unittest machines which obey clobber files anymore. Clobber support for 3.1/3.2 will be coming as part of https://bugzilla.mozilla.org/show_bug.cgi?id=432236
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.