Closed Bug 846216 Opened 12 years ago Closed 10 years ago

Errors in cfx testaddons are not printed and don't timeout

Categories

(Add-on SDK Graveyard :: General, defect, P1)

Product:
Add-on SDK Graveyard
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: evold, Unassigned)

References

Details

Errors occurring in a test addon test that uses the done() method (ie is async) do not print and I don't think they timeout either, so when this happens I have to manually close the browser window to get the tests running again.
Do they really not timeout, or are they just on a really long timeout?
Flags: needinfo?(evold)
Priority: -- → P1
Summary: Errors is cfx testaddons are printed and don't timeout → Errors in cfx testaddons are not printed and don't timeout
so the timeouts happen, but they take about an hour.
Flags: needinfo?(evold)
That's the 1800 second timeout, right?
the timeout took 3999 secs as I recall.
This seems related to bug 926264
wontfixing this cfx bug, since the errors will be caught in the machitestification test suite or the travis test suite.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.