Closed
Bug 1145616
Opened 10 years ago
Closed 10 years ago
Test failure 'notification is undefined' in testPreferencesMasterPassword.js and testPasswordSavedAndDeleted.js
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect, P1)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(firefox39 fixed)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox39 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
(Keywords: regression, Whiteboard: [mozmill-test-failure])
Attachments
(1 file)
2.42 KB,
patch
|
Details | Diff | Splinter Review |
We have a new regression in our test for todays Nightly build. Looks like a change in the password manager code causes us to fail with this failure:
ERROR | Test Failure | {
"exception": {
"message": "notification is undefined",
"lineNumber": 912,
"name": "TypeError",
"fileName": "resource://mozmill/stdlib/securable-module.js -> file:///home/mozauto/jenkins/workspace/mozilla-central_functional/data/mozmill-tests/firefox/lib/toolbars.js"
}
Maybe they renamed the id of the notification or such. Should be easy to find out.
Assignee | ||
Comment 1•10 years ago
|
||
Pushlog for Nightly builds between March 19th and March 20th:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=cf1060d8ce9f&tochange=4d2d97b3ba34
Bug 1143852 seems to be the regressor here. Looks like it can be fixed quickly. I will try. Otherwise we have to skip those tests forever.
Keywords: regressionwindow-wanted
Assignee | ||
Comment 2•10 years ago
|
||
A fix is upcoming.
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Summary: Test failure 'notification is undefined' in testPreferencesMasterPassword.s and testPasswordSavedAndDeleted.js → Test failure 'notification is undefined' in testPreferencesMasterPassword.js and testPasswordSavedAndDeleted.js
Assignee | ||
Comment 3•10 years ago
|
||
This is the bustage fix for our tests.
Assignee | ||
Comment 4•10 years ago
|
||
Landed on default:
https://hg.mozilla.org/qa/mozmill-tests/rev/9c4363786ee3
Blocks: 1143852
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
status-firefox39:
--- → fixed
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•