Closed Bug 1132169 Opened 9 years ago Closed 8 years ago

Intermittent test_WebCrypto.html,test_WebCrypto_DH.html,test_WebCrypto_ECDH.html,test_WebCrypto_JWK.html | Test timed out | [SimpleTest.finish()] waitForFocus() was called from a stray Windows Firewall dialog in front of the window

Categories

(Core :: DOM: Security, defect, P3)

x86
Windows XP
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: RyanVM, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [domsecurity-intermittent])

Attachments

(1 file)

07:35:51 INFO - 1 INFO TEST-START | dom/crypto/test/test_WebCrypto.html
07:40:54 INFO - 2 INFO Error: Unable to restore focus, expect failures and timeouts.
07:40:54 INFO - 3 INFO must wait for focus
07:40:54 INFO - 4 INFO TEST-UNEXPECTED-FAIL | dom/crypto/test/test_WebCrypto.html | Test timed out. - expected PASS
07:40:55 INFO - 5 INFO TEST-UNEXPECTED-FAIL | dom/crypto/test/test_WebCrypto.html | [SimpleTest.finish()] waitForFocus() was called a different number of times from the number of callbacks run. Maybe the test terminated prematurely -- be sure to use SimpleTest.waitForExplicitFinish(). - got 1, expected 0
07:40:55 INFO - 6 INFO MEMORY STAT vsize after test: 402194432
07:40:55 INFO - 7 INFO MEMORY STAT vsizeMaxContiguous after test: 880803840
07:40:55 INFO - 8 INFO MEMORY STAT residentFast after test: 192180224
07:40:55 INFO - 9 INFO MEMORY STAT heapAllocated after test: 38868940
07:40:55 INFO - 10 INFO TEST-OK | dom/crypto/test/test_WebCrypto.html | took 303895ms
07:40:58 INFO - 11 INFO Error: Unable to restore focus, expect failures and timeouts.
07:40:58 INFO - 12 INFO TEST-UNEXPECTED-FAIL | dom/crypto/test/test_WebCrypto.html | [SimpleTest.finish()] waitForFocus() was called a different number of times from the number of callbacks run. Maybe the test terminated prematurely -- be sure to use SimpleTest.waitForExplicitFinish(). - Result logged after SimpleTest.finish()
Because of the charming ways of WinXP, where an OOM program will frequently but not always crawl back to the back of the running program stack, the firewall dialog may have nothing at all to do with this, other than having just been innocently hiding behind the browser window until an OOM pulled the browser back and forced it to be topmost.
See Also: → 1143124
Component: DOM: Security → Security
Component: Security → DOM: Security
Whiteboard: [domsecurity-intermittent]
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: