Closed Bug 452147 Opened 16 years ago Closed 16 years ago

SeaMonkey debug build tinderbox needed

Categories

(SeaMonkey :: Build Config, defect)

defect
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED
seamonkey2.0b1

People

(Reporter: mnyromyr, Assigned: kairo)

References

Details

As bug 451903 clearly shows, we need a way to visibly catch build regressions in debug builds. For starters, any OS would probably do, to catch at least e.g. regressions with MailNews' non-static debug libraries. (Since TB hasn't got any debug tinderboxen, see bug 420317 and bug 428398, such regressions creep in easily and unnoticed.) (I'm not sure at all if this is the right component, please reassign as you see fit.)
We'd need additional buildbot slave machines for providing such builds.
(In reply to comment #0) [...] > (I'm not sure at all if this is the right component, please reassign as you see > fit.) > Not sure either, but maybe in Product=mozilla.org, one of the "Release engineering" or "Server operations" components?
Assignee: general → build-config
Component: General → Build Config
QA Contact: general → build-config
New debug breakage on Tinderboxen green: bug 456466 / bug 456483.
Assignee: build-config → server-ops
Component: Build Config → Server Operations
Product: SeaMonkey → mozilla.org
QA Contact: build-config → mrz
Summary: debug tinderbox needed → debug tinderbox needed (comm-central?)
Version: Trunk → other
Assignee: server-ops → nobody
Component: Server Operations → Release Engineering
QA Contact: mrz → release
Seamonkey is a community project, so it belongs in that Product in bugzilla. If KaiRo has a specific request for IT, then he can make it and move the bug over to them.
Assignee: nobody → build-config
Component: Release Engineering → Build Config
Product: mozilla.org → SeaMonkey
QA Contact: release → build-config
Version: other → unspecified
Version: unspecified → Trunk
(Also related is bug 372581 about test boxes.)
Summary: debug tinderbox needed (comm-central?) → debug build tinderbox needed (comm-central?)
CC Marcia, as we briefly spoke about it at "Mozilla Camp Europe 2008". (Started as SeaMonkey, but may apply to Firefox and/or Thunderbird too.)
(In reply to comment #6) > (Started as SeaMonkey, but may apply to Firefox and/or Thunderbird too.) Firefox has debug tinderboxes in the form of the Leak & Bloat boxes. Thunderbird will have these within the next few days if all goes well. So SeaMonkey is the only issue here.
Depends on: 464325
Blocks: 492221
We now have a machine for that and a Leak & Bloat config enabled in the buildbots that are for the moment reporting to the SeaMonkey-Ports waterfall. The only reason it reports red for the moment is bug 492221 (failing graph data upload). This bug for itself is fixed, IMHO, even though the new buildbots are not really "production" yet but somewhat experimental.
Assignee: build-config → kairo
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Ftr, this is { Linux comm-central leak test build Building on: cb-seamonkey-linux-01 } V.Fixed.
Status: RESOLVED → VERIFIED
Flags: in-testsuite-
Summary: debug build tinderbox needed (comm-central?) → SeaMonkey debug build tinderbox needed
Target Milestone: --- → seamonkey2.0b1
"Linux comm-central leak test build" is correct, the "Building on:" can be any of cb-seamonkey-linuxdebug-01 (the box originally thought for this), cb-seamonkey-linux-01 or cb-seamonkey-linux-02 - the three boxes share the duty of doing everything that comes up for Linux on that master.
You need to log in before you can comment on or make changes to this bug.