Closed Bug 1565363 Opened 5 years ago Closed 5 years ago

Intermittent toolkit/components/passwordmgr/test/browser/{browser_generated_password_doorhangers.js,browser_doorhanger_generated_password.js} | Test timed out -

Categories

(Toolkit :: Password Manager, defect, P5)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Regression)

Details

(Keywords: intermittent-failure, regression, Whiteboard: [test isolation])

Filed by: rgurzau [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=256004412&repo=autoland
Full log: https://queue.taskcluster.net/v1/task/EsO3e5TXTjGwupxTT2-ulw/runs/0/artifacts/public/logs/live_backing.log


19:28:20 INFO - TEST-PASS | toolkit/components/passwordmgr/test/browser/browser_generated_password_doorhangers.js | Doorhanger password field has generated 15-char value -
19:28:20 INFO - TEST-PASS | toolkit/components/passwordmgr/test/browser/browser_generated_password_doorhangers.js | Doorhanger username field has the username field value -
19:28:20 INFO - Leaving test bound contextfill_generated_password_with_username
19:28:20 INFO - Entering test bound autocomplete_generated_password
19:28:20 INFO - Buffered messages logged at 19:26:53
19:28:20 INFO - TEST-PASS | toolkit/components/passwordmgr/test/browser/browser_generated_password_doorhangers.js | Got popup -
19:28:20 INFO - content window focused
19:28:20 INFO - TEST-PASS | toolkit/components/passwordmgr/test/browser/browser_generated_password_doorhangers.js | autocomplete popup shown -
19:28:20 INFO - TEST-PASS | toolkit/components/passwordmgr/test/browser/browser_generated_password_doorhangers.js | Got generated password richlistitem -
19:28:20 INFO - Clicking the generated password AC item
19:28:20 INFO - Waiting for the content input value to change
19:28:20 INFO - Buffered messages finished
19:28:20 INFO - TEST-UNEXPECTED-FAIL | toolkit/components/passwordmgr/test/browser/browser_generated_password_doorhangers.js | Test timed out -
19:28:20 INFO - GECKO(5436) | MEMORY STAT | vsize 929MB | vsizeMaxContiguous 541MB | residentFast 308MB | heapAllocated 89MB
19:28:20 INFO - TEST-OK | toolkit/components/passwordmgr/test/browser/browser_generated_password_doorhangers.js | took 90038ms
19:28:20 INFO - Not taking screenshot here: see the one that was previously logged
19:28:20 INFO - TEST-UNEXPECTED-FAIL | toolkit/components/passwordmgr/test/browser/browser_generated_password_doorhangers.js | Found a tab after previous test timed out: https://example.com/browser/toolkit/components/passwordmgr/test/browser/form_basic.html -
19:28:20 INFO - GECKO(5436) | [Parent 2608, Main Thread] WARNING: Constructing RangeBoundary with invalid value: 'mRef || aOffset == 0', file z:/build/build/src/obj-firefox/dist/include\mozilla/RangeBoundary.h, line 79
19:28:20 INFO - GECKO(5436) | [Parent 2608, Main Thread] WARNING: Constructing RangeBoundary with invalid value: 'mRef || aOffset == 0', file z:/build/build/src/obj-firefox/dist/include\mozilla/RangeBoundary.h, line 79
19:28:20 INFO - GECKO(5436) | [Child 5676, Main Thread] WARNING: No active window: file z:/build/build/src/js/xpconnect/src/XPCJSContext.cpp, line 662

Type: -- → defect
Whiteboard: [test isolation]
See Also: → 1571217
Whiteboard: [test isolation][stockwell disable-recommended] → [test isolation]
Summary: Intermittent toolkit/components/passwordmgr/test/browser/browser_generated_password_doorhangers.js | Test timed out - → Intermittent toolkit/components/passwordmgr/test/browser/{browser_generated_password_doorhangers.js,browser_doorhanger_generated_password.js} | Test timed out -
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE

Sam can you take a look?

Flags: needinfo?(sfoster)
Regressed by: 1618696

(In reply to Andreea Pavel [:apavel] from comment #25)

Sam can you take a look?

Isn't this the same issue as bug 1621191 - looks to me like the test is running out of time to complete, not that individual tests are failing?
There are a lot of tasks in that test file now, and some negative tests need to wait to ensure something doesnt happen, which adds up.
Splitting up the test needs a refactor that'll take a little time - I'll try the longer timeout first.

Flags: needinfo?(sfoster)
Status: REOPENED → RESOLVED
Closed: 5 years ago5 years ago
Resolution: --- → INCOMPLETE
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.