Closed Bug 919425 Opened 12 years ago Closed 12 years ago

Test failure 'Shutdown expected but none detected before timeout' in /restartTests/testAddons_enableDisableExtension/test3.js

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect, P4)

Product:
Mozilla QA Graveyard
Component:
Mozmill Tests
Platform:
All
Windows 8
Type:
defect

Tracking

(firefox24 ?, firefox25 ?, firefox26 affected, firefox27 ?, firefox-esr17 ?)

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox24 --- ?
firefox25 --- ?
firefox26 --- affected
firefox27 --- ?
firefox-esr17 --- ?

People

(Reporter: andrei, Unassigned)

References

(
URL
)

Details

(Whiteboard: [mozmill-test-failure])

Module: teardownModule Test: testAddons_enableDisableExtension/test3.js Failure: Shutdown expected but none detected before timeout Branches: mozilla-aurora Platforms: Windows 8 After the mentioned shutdown failure, we see "Disconnect Error: Application unexpectedly closed" Report: http://mozmill-daily.blargon7.com/#/functional/report/1039ea48a9d69a5a1cc4fd228c9a9902
status-firefox24: --- → ?
status-firefox25: --- → ?
status-firefox26: --- → affected
status-firefox27: --- → ?
status-firefox-esr17: --- → ?
Priority: -- → P3
Have you checked the node mm-win-81-32-1? It's running at 100% cpu load. I'm going to restart it. It most likely will fix it.
Severity: normal → critical
Machine has been restarted. We should no longer experience this issue for now.
Did not happen again since last week, but lets keep an eye on it a bit more before closing as WFM.
Severity: critical → normal
Priority: P3 → P4
No additional failures, was probably due to the high CPU load we experienced that week.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.