Closed Bug 385276 Opened 17 years ago Closed 14 years ago

Something should turn orange when reftests are hitting assertions

Categories

(Testing :: Reftest, defect)

Product:
Testing
Component:
Reftest
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jruderman, Unassigned)

References

(Blocks 1 open bug)

Details

I wasted an hour or two today making/finding testcases for bug 385265 and bug 385270.  When I was halfway through making a testcase for the latter, I realized that reftests would probably hit it, so I ran reftests on my machine instead of trying to create a testcase another way.

If Tinderbox had turned orange, I wouldn't have had to waste all that time and roc would have known about the bugs sooner.

This might sorta-depend on bug 368573.
Depends on: 415388
Depends on: 414321
Depends on: 448612
Depends on: 404693
Depends on: 468690
Depends on: 469243
Component: Testing → Reftest
Product: Core → Testing
QA Contact: testing → reftest
Depends on: 472502
dbaron has the reftest code in bug 472557, but we'll need a debug tinderbox running unit tests to get any use out of it.
Depends on: 477929
Depends on: 489479
Depends on: 495328
Depends on: 540367
We have debug tinderboxen for all platforms now :)
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.