Closed Bug 187015 Opened 17 years ago Closed 4 years ago

Track the compiler 'Build Warnings' count.

Categories

(Webtools Graveyard :: Tinderbox2, enhancement)

x86
Linux
enhancement
Not set

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mozilla-bugs, Assigned: kestes)

References

(Depends on 1 open bug)

Details

On Tbox-1 there used to be couple of boxed (brad and another one) that would
always show the current warning count in the build. That made it easy to see
when some commit added a lot of warnings; it also prompted some people to try to
reduce the number of warnings.

Can a similar counter be added to Tbox-2 (for those machines that do a clobber
build, such as brad)?
Blocks: buildwarning
No longer blocks: buildwarning
Depends on: buildwarning
Summary: Please track the warnings count. → Please track the compiler 'Build Warnings' count.
We no longer have a tbox2 install.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Actually, this is a feature request that could be valid for tbox2 in general and
not just specifically ours...  let me fix the component instead.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Assignee: endico → kestes
Status: REOPENED → NEW
Component: Tinderbox Configuration → Tinderbox2
Product: mozilla.org → Webtools
QA Contact: mcafee
Summary: Please track the compiler 'Build Warnings' count. → Track the compiler 'Build Warnings' count.
QA Contact: tinderbox2
Depends on: 231998
I suggest we WONTFIX this in favour of bug 703121 which would provide a much stronger mechanism to prevent new warnings being introduced.
Product: Webtools → Webtools Graveyard
As per comment 3: WONTFIX. WARNINGS_AS_ERRORS, now inverted and called ALLOW_COMPILER_WARNINGS, is much better.
Status: NEW → RESOLVED
Closed: 15 years ago4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.