Closed Bug 729040 Opened 13 years ago Closed 12 years ago

Mozmill test failure //testAwesomeBar/testGoButton.js | controller.assertJS: Failed for 'subject.visible == subject.expectedVisibility'

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

x86
Linux
defect
Not set
normal

Tracking

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

RESOLVED WORKSFORME
Tracking Status
firefox13 --- fixed
firefox14 --- fixed
firefox15 --- fixed
firefox16 --- fixed
firefox-esr10 --- unaffected

People

(Reporter: vladmaniac, Assigned: AlexLakatos)

References

Details

(Whiteboard: [mozmill-test-failure])

Attachments

(1 file, 1 obsolete file)

Firefox version: Firefox 13.0a1 (13.0a1, en-US, 20120218031156) ----------------------------------------------------------------------------- Platform: All ----------------------------------------------------------------------------- Mozmill version: 1.5.7 ----------------------------------------------------------------------------- First started failling: 2012/02/18 ----------------------------------------------------------------------------- Currently failling on Nightly/default branch ----------------------------------------------------------------------------- Report: http://mozmill-release.blargon7.com/#/functional/report/55d601cc2aabfac28f59060a84a11ad4 ----------------------------------------------------------------------------- Error: assert((function () {return eval(expression);}),"controller.assertJS: Failed for 'subject.visible == subject.expectedVisibility'")@resource://mozmill/modules/utils.js:395 ("subject.visible == subject.expectedVisibility",[object Proxy])@resource://mozmill/modules/controller.js:931
The fix for this test would definitely depend on Alex's assertJS refactoring patch. I'll investigate bug 729037 see if the patch for that helps or fixes this one too. If not assigning to Alex later today for investigation/fix/skip the test
Depends on: 724713
Whiteboard: [mozmill-test-failure][mozmill-functional]
Skipping the test until I resolve the dependency.
Assignee: nobody → alex.lakatos
Status: NEW → ASSIGNED
Attachment #599137 - Flags: review?(anthony.s.hughes)
Comment on attachment 599137 [details] [diff] [review] skipPatch v1.0 [landed:default,aurora,beta] Landed: http://hg.mozilla.org/qa/mozmill-tests/rev/7022a1b9997e (default)
Attachment #599137 - Attachment description: skipPatch v1.0 → skipPatch v1.0 [landed]
Attachment #599137 - Flags: review?(anthony.s.hughes) → review+
Whiteboard: [mozmill-test-failure][mozmill-functional] → [mozmill-test-failure][mozmill-test-skipped]
Comment on attachment 599137 [details] [diff] [review] skipPatch v1.0 [landed:default,aurora,beta] Note, as per recent merges, this test is now disabled on Nightly, Aurora, and Beta.
Attachment #599137 - Attachment description: skipPatch v1.0 [landed] → skipPatch v1.0 [landed:default,aurora,beta]
Alex, any update on this bug?
It's been almost two weeks since Henrik's reminder. Any updates?
Attached patch patch v1.0 (obsolete) — Splinter Review
(In reply to Dave Hunt (:davehunt) [away until 14th June] from comment #6) > It's been almost two weeks since Henrik's reminder. Any updates? The comment seems to have fallen through my mail filters. This does not fail anymore, so here is the patch that enables it and cleans the litmus reference.
Attachment #633992 - Flags: review?
Attachment #633992 - Flags: review? → review?(dave.hunt)
Comment on attachment 633992 [details] [diff] [review] patch v1.0 We do not need a separate patch. We will backout the original patch instead. Do you have any reports which show that this test is no longer failing?
Attachment #633992 - Attachment is obsolete: true
Attachment #633992 - Flags: review?(dave.hunt)
(In reply to Henrik Skupin (:whimboo) from comment #8) > Comment on attachment 633992 [details] [diff] [review] > patch v1.0 > > We do not need a separate patch. We will backout the original patch instead. > Do you have any reports which show that this test is no longer failing? Yes, here is one. http://mozmill-crowd.blargon7.com/#/functional/report/8bf3fa70d3d9a46d3e7617383b1161c6
This has to be tested across all platforms. Otherwise it's too risky to re-enable the test.
Tested across MacOSX, Win 7 and Windows XP. They all passed. But seeing as how http://mozmill-crowd.blargon7.com/ is still down, I can't attach links. I will re-run them once the dashboard is up, so we can have reports.
The IrisCouch outage has been fixed. So please re-run as soon as possible so we could have this test enabled for the tests today.
Sounds good. But next time please make sure to update the local repository before running the tests. At least the last one is really outdated. Pushed: http://hg.mozilla.org/qa/mozmill-tests/rev/fdb54e829795 (default) Alex please check which branches are affected and would need this to be backed-out. Also please reference the changesets because I only see one for default.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Resolution: FIXED → WORKSFORME
Dave, can you please transplant the patch to the affected branches?
Alex, please re-enable all the litmus tests.
Flags: in-litmus?(alex.lakatos)
Whiteboard: [mozmill-test-failure][mozmill-test-skipped] → [mozmill-test-failure]
Alex, please check the flags when updating the litmus tests. It's missing an update for Firefox 13.
Flags: in-litmus+ → in-litmus?(alex.lakatos)
The test for the Firefox 13 Branch did not need updating, I checked. That's why I only pasted the two links. https://litmus.mozilla.org/show_test.cgi?id=55416
Flags: in-litmus?(alex.lakatos) → in-litmus+
Always paste all the litmus test URLs of the affected branches. Only that way we can verify it correctly. Thanks.
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: