Closed Bug 1122478 Opened 9 years ago Closed 5 years ago

Fix newtab browser chrome tests to run on OS X 10.10

Categories

(Firefox :: New Tab Page, defect)

x86
macOS
defect
Not set
normal
Points:
8

Tracking

()

RESOLVED INVALID

People

(Reporter: Gijs, Unassigned)

References

Details

https://treeherder.mozilla.org/ui/logviewer.html#?job_id=91809&repo=cedar

22:12:02 INFO - 701 INFO TEST-UNEXPECTED-FAIL | browser/base/content/test/newtab/browser_newtab_drag_drop.js | Test timed out - expected PASS
22:12:02 INFO - JavaScript error: resource://gre/components/contentAreaDropListener.js, line 126: TypeError: sourceDocument.defaultView is null
22:12:02 INFO - 702 INFO TEST-UNEXPECTED-FAIL | browser/base/content/test/newtab/browser_newtab_drag_drop.js | uncaught exception - NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS: [JavaScript Error: "sourceDocument.defaultView is null" {file: "resource://gre/components/contentAreaDropListener.js" line: 126}]'[JavaScript Error: "sourceDocument.defaultView is null" {file: "resource://gre/components/contentAreaDropListener.js" line: 126}]' when calling method: [nsIDroppedLinkHandler::canDropLink] at chrome://global/content/bindings/browser.xml:1215
22:12:02 INFO - Stack trace:
22:12:02 INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:simpletestOnerror:1474
22:12:02 INFO - chrome://mochitests/content/browser/browser/base/content/test/newtab/head.js:synthesizeNativeMouseEvent:618
22:12:02 INFO - chrome://mochitests/content/browser/browser/base/content/test/newtab/head.js:synthesizeNativeMouseDrag:590
22:12:02 INFO - chrome://mochitests/content/browser/browser/base/content/test/newtab/head.js:startAndCompleteDragOperation/interval<:508
22:12:02 INFO - null:null:0 

times a lot, for all the tests involving dnd, followed by crash in browser_newtab_update.js:

22:21:30 INFO - 2015-01-15 22:21:30: stackwalker.cc:125: INFO: Couldn't load symbols for: /builds/slave/talos-slave/test/build/application/Nightly.app/Contents/MacOS/libmozglue.dylib|76A06B784DCC3C97915FFC3426E355B30
22:22:28 INFO - TEST-INFO | Main app process: killed by SIGHUP
22:22:28 INFO - 51955 ERROR TEST-UNEXPECTED-FAIL | browser/base/content/test/newtab/browser_newtab_update.js | application terminated with exit code 1
22:22:28 INFO - runtests.py | Application ran for: 0:12:11.844086
22:22:28 INFO - zombiecheck | Reading PID log: /var/folders/c6/rs25l9515k541zfkp3mq7x4c00000w/T/tmpD0HqFGpidlog
22:22:28 INFO - mozcrash Downloading symbols from: https://ftp-ssl.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/cedar-macosx64/1421359890/firefox-38.0a1.en-US.mac.crashreporter-symbols.zip
22:22:52 INFO - mozcrash Saved minidump as /builds/slave/talos-slave/test/build/blobber_upload_dir/FA014471-AF36-4156-AFE3-3A751F303D27.dmp
22:22:52 INFO - mozcrash Saved app info as /builds/slave/talos-slave/test/build/blobber_upload_dir/FA014471-AF36-4156-AFE3-3A751F303D27.extra
22:22:52 WARNING - PROCESS-CRASH | browser/base/content/test/newtab/browser_newtab_update.js | application crashed [@ mozilla::(anonymous namespace)::RunWatchdog(void*)] 



Same story on debug:

https://treeherder.mozilla.org/ui/logviewer.html#?job_id=91373&repo=cedar
Kim, is it possible to push to try and get 10.10 builds+tests to run at all?
Points: --- → 8
Flags: needinfo?(kmoir)
Flags: firefox-backlog+
The patches to run hidden 10.10 tests on try are awaiting review in bug 1122039. Once they are in production you should be able to run them on try.
Flags: needinfo?(kmoir)
You can run them on try like this

try:  -b do -p macosx64 -u mochitest-browser-chrome-1[10.10] -t none
Disabled in https://hg.mozilla.org/integration/mozilla-inbound/rev/63e80b49bc19 so I don't have to keep looking through several hundred test failures and a shutdown crash to be sure they haven't changed to several hundred and one test failures and a different shutdown crash.

So you can reenable and run them on try by sticking https://hg.mozilla.org/try/rev/01ac92126030 at the top of your patch queue.
Keywords: leave-open
Flags: qe-verify-
No longer blocks: 1121199
The leave-open keyword is there and there is no activity for 6 months.
:tspurway, maybe it's time to close this bug?
Flags: needinfo?(tspurway)
Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(tspurway)
Resolution: --- → INVALID
Resolution: INVALID → INACTIVE
Invalid was the right resolution here, as these tests have been removed.
Resolution: INACTIVE → INVALID
You need to log in before you can comment on or make changes to this bug.