Failure in testPasswordManager :: testPasswordNotSaved

VERIFIED FIXED

Status

VERIFIED FIXED
7 years ago
7 years ago

People

(Reporter: ashughes, Assigned: AlexLakatos)

Tracking

unspecified
x86
macOS
Bug Flags:
in-litmus +

Firefox Tracking Flags

(firefox13 fixed, firefox14 fixed, firefox15 fixed, firefox16 fixed, firefox-esr10 fixed)

Details

(Whiteboard: [mozmill-test-failure], URL)

Attachments

(1 attachment)

(Reporter)

Description

7 years ago
This just started happening recently on Nightly and Aurora though intermittently. It appears to be Mac only.

Test: testPasswordManager :: testPasswordNotSaved.js :: testPasswordNotSaved()
Fail: Pane has been changed - expected 'panePrivacy'
Assigning to Alex
Assignee: nobody → alex.lakatos
Status: NEW → ASSIGNED
(Assignee)

Comment 2

7 years ago
Created attachment 581694 [details] [diff] [review]
disable test: default/aurora [checked-in]

I could not figure out the issue. I'm still investigating, but skipping the test for now, as to our policy.
Attachment #581694 - Flags: review?(anthony.s.hughes)
(Reporter)

Updated

7 years ago
Attachment #581694 - Flags: review?(anthony.s.hughes) → review+
(Reporter)

Comment 3

7 years ago
Comment on attachment 581694 [details] [diff] [review]
disable test: default/aurora [checked-in]

Landed:
http://hg.mozilla.org/qa/mozmill-tests/rev/43597e45052b (default)
http://hg.mozilla.org/qa/mozmill-tests/rev/dfabcd7f5ecf (mozilla-aurora)
Attachment #581694 - Attachment description: skipPatch v1.0 → disable test: default/aurora [checked-in]
(Reporter)

Updated

7 years ago
Whiteboard: [mozmill-test-failure] → [mozmill-test-failure][mozmill-test-skipped]
(Assignee)

Comment 4

7 years ago
I ran this today on Lion, 100 times for each branch. And out of that it only failed once on Nightly. Can we unskip the test?
(Reporter)

Comment 5

7 years ago
(In reply to Alex Lakatos[:AlexLakatos] from comment #4)
> I ran this today on Lion, 100 times for each branch. And out of that it only
> failed once on Nightly. Can we unskip the test?

Were you able to reproduce the failure locally before this test was skipped?
(Assignee)

Comment 6

7 years ago
(In reply to Anthony Hughes, Mozilla QA (irc: ashughes) from comment #5)
> Were you able to reproduce the failure locally before this test was skipped?
It was failing more than once during 200 runs. But not a lot more. I could not reproduce the failure when running the test once, instead of running it in a for loop.
(Reporter)

Comment 7

7 years ago
Then I would say the situation has not improved, and since there is no change in Firefox code we can't just re-enable the test. Until we can figure out why it intermittently fails we cannot re-enable this test.
Please check out bug 671382. I'm working to fix the paneId setter right now.
Taking all the failures into consideration, I'll double the efforts with Alex's help in finding a robust fix.
Alex, do you have an update for us?
Any updates?
(Assignee)

Comment 11

7 years ago
It's passing now, but I'm still running it over and over to determine if we are safe to re-enable it.
(Assignee)

Comment 13

7 years ago
Based on Comment 12, I think we're safe to re-enable it for default and go from there. Henrik, what do you think?
Ok, lets try that. Landed on default as:
http://hg.mozilla.org/qa/mozmill-tests/rev/1397c0ccc72a

Alex, please check which branches are affected. I assume all of the supported ones. If it sticks green we can transplant to older branches by mid of this week.
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
status-firefox16: --- → fixed
Resolution: --- → FIXED
(Assignee)

Updated

7 years ago
status-firefox-esr10: --- → affected
status-firefox13: --- → affected
status-firefox14: --- → affected
status-firefox15: --- → affected
(Assignee)

Comment 15

7 years ago
(In reply to Henrik Skupin (:whimboo) from comment #14)
> Ok, lets try that. Landed on default as:
> http://hg.mozilla.org/qa/mozmill-tests/rev/1397c0ccc72a
> 
> Alex, please check which branches are affected. I assume all of the
> supported ones. If it sticks green we can transplant to older branches by
> mid of this week.
Latest run in CI passes.
http://mozmill-ci.blargon7.com/#/functional/report/9acea0c923846813ba8ce41994000af5

This needs to land on aurora, beta, release and esr10.
Pushed:
http://hg.mozilla.org/qa/mozmill-tests/rev/c55ad3bc7803 (aurora)
http://hg.mozilla.org/qa/mozmill-tests/rev/e9af10605968 (beta)
http://hg.mozilla.org/qa/mozmill-tests/rev/b570a5a1027c (release)
http://hg.mozilla.org/qa/mozmill-tests/rev/799e387e806a (esr10)

Please update all the Litmus tests which are disabled.
status-firefox-esr10: affected → fixed
status-firefox13: affected → fixed
status-firefox14: affected → fixed
status-firefox15: affected → fixed
Flags: in-litmus?(alex.lakatos)
Whiteboard: [mozmill-test-failure][mozmill-test-skipped] → [mozmill-test-failure]
An update for the litmus testcase of the esr10 branch is still missing.
Flags: in-litmus+ → in-litmus?(alex.lakatos)
(Assignee)

Comment 19

7 years ago
I'm not seeing an esr branch in litmus. There are several tests for the aurora branch, but I can't see an esr branch.
This is Firefox 10.0!
(Assignee)

Comment 21

7 years ago
Edited this a while back but seems I forgot to flip the flag.
https://litmus.mozilla.org/show_test.cgi?id=40737
Flags: in-litmus?(alex.lakatos) → in-litmus+
You need to log in before you can comment on or make changes to this bug.