Closed Bug 442122 Opened 16 years ago Closed 16 years ago

"Unable to restore focus" test failure not counted in mochitest summary

Categories

(Testing :: Mochitest, defect)

Product:
Testing
Component:
Mochitest
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: ted, Unassigned)

References

(
URL
)

Details

(Keywords: intermittent-failure) 

The error log contains:
*** 495 ERROR FAIL | Unable to restore focus, expect failures and timeouts. |  | chrome://mochikit/content/chrome/toolkit/content/tests/chrome/test_bug331215.xul

and the build is orange, but the tinderbox waterfall shows:
  L-
rev:dfb267af6f44
TUnit
552/0
reftest
1952/0/72
crashtest
679/0/0
mochitest
51677/0/1140
chrome
692/0/27
browser
367/0/3 

so somehow it miscounted?
I think this is a bug in Mochitest, since the count is generated there, and it doesn't count these failures.
Component: Release Engineering → Testing
Product: mozilla.org → Core
QA Contact: release → testing
Version: other → Trunk
Component: Testing → Mochitest
Product: Core → Testing
QA Contact: testing → mochitest
Summary: unit test box not reporting test failure correctly in summary on tinderbox waterfall → "Unable to restore focus" test failure not counted in mochitest summary
Version: Trunk → unspecified
This would help debug "intermittent" unittest failures.
Blocks: 438871
Did this get covered in the big error consolidation patch?
It's a different bug. I threw out a proposal over in bug 442125 that might invalidate this one.

This should no longer be a problem with the fix from bug 442125 in.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.