Closed Bug 754578 Opened 12 years ago Closed 6 years ago

[SeaMonkey] mochitest-chrome: "test_cross_domain.xul | Test timed out" (+ 3+ more)


(Core Graveyard :: DOM: Apps, defect)

Not set



Tracking Status
firefox15 - ---


(Reporter: sgautherie, Unassigned)


(Blocks 1 open bug)


(Whiteboard: [perma-orange] [test which aborts the suite])

9871 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/dom/tests/mochitest/webapps/test_cross_domain.xul | Test timed out.
9874 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/dom/tests/mochitest/webapps/test_install_app.xul | Test timed out.
9877 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/dom/tests/mochitest/webapps/test_install_errors.xul | Test timed out.
9880 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/dom/tests/mochitest/webapps/test_install_receipts.xul | Test timed out.
9881 ERROR TEST-UNEXPECTED-FAIL | (SimpleTest/TestRunner.js) | 4 test timeouts, giving up.
Whiteboard: [perma-orange] → [perma-orange] [test which aborts the suite]
Summary: [SeaMonkey] "test_cross_domain.xul | Test timed out" (+ 3+ more) → [SeaMonkey] mochitest-chrome: "test_cross_domain.xul | Test timed out" (+ 3+ more)
Would this be caused by lack of bug 735571 (not handled by tests)?
can we make it so these tests only run on the browser .. not sure why we would run these against sea monkey ?
It's not clear that this affects FF tests. No need to track for the release of Firefox.
A bugfix in the webapps code makes this a perma orange on try.
What's the state here? Did we disable this tests on mc?
Looks like 7166a68a7994 Jason Orendorff – Bug 750307 in TRY server which is being backed out
(In reply to from comment #2)
> can we make it so these tests only run on the browser .. not sure why we
> would run these against sea monkey ?

dclarke, these tests run in SeaMonkey because SeaMonkey is a community browser+mail client.

If the functionality is Firefox ONLY and not meant to be useable by anything built off of Gecko directly, then we should identify that and block these tests out for Firefox Only.

If it just needs some SeaMonkey UI support to go along with the Gecko Feature, than we can do that.

If it shouldn't need explicit UI support than we would appreciate help in identifying why these are failing.
actually... noticing

along with

Makes me think that if we just port a stub, without real UI, that returns "true" if the dry-run pref is set we might be able to pass these tests (caveat just glancing at code)
(In reply to TinderboxPushlog Robot from comment #13)
> ehsan
> Inbound

Not this bug.
Severity: major → normal
Component: DOM: Mozilla Extensions → DOM: Apps
Priority: P2 → --
Target Milestone: mozilla15 → ---
Severity: normal → major
Priority: -- → P2
Target Milestone: --- → mozilla15
Let's keep the priority and milestone fields unset. We haven't triaged this bug (yet, but I'm working on fixing that problem).
Priority: P2 → --
Target Milestone: mozilla15 → ---
Sorry, disregard comment 16, was mis-star and fixed by backout:
Product: Core → Core Graveyard
Core Graveyard / DOM: Apps is inactive. Closing all bugs in this component.
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.