Closed Bug 446333 Opened 16 years ago Closed 14 years ago

unit tests should TinderboxPrint something if the testsuite crashes

Categories

(Release Engineering :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ted, Unassigned)

Details

Right now if a testsuite crashes, we get orange with nothing visible on Tinderbox as to why it failed. (You can look in the log and see the segfault or whatever, usually.) We should "TinderboxPrint: CRASHED".
P3-Future for now. If this blocks debugging the intermittent unittests, then we should revisit. 
Component: Release Engineering → Release Engineering: Future
Priority: -- → P3
What do you mean by "if this blocks debugging the intermittent unittests"? It certainly does.
Component: Release Engineering: Future → Release Engineering
Priority: P3 → --
Assignee: nobody → lukasblakk
Priority: -- → P2
Status: NEW → ASSIGNED
I wrote a patch with intentionally crashing tests for lsblakk to use in testing:
http://people.mozilla.com/~tmielczarek/crashy-tests.patch
Working on other stuff right now, will get back to this.
Assignee: lukasblakk → nobody
Component: Release Engineering → Release Engineering: Future
Priority: P2 → P3
I'm not sure what bugs they happened in, but we have this for everything except Tunit now.
Mass move of bugs from Release Engineering:Future -> Release Engineering. See
http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.
Component: Release Engineering: Future → Release Engineering
Status: ASSIGNED → NEW
If this is still happening anywhere, please file new bugs.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.