Closed Bug 1369982 Opened 4 years ago Closed 4 years ago

TEST-UNEXPECTED-FAIL | toolkit/components/crashes/tests/xpcshell/test_crash_service.js | xpcshell return code: 0


(Thunderbird :: Testing Infrastructure, defect)

Not set


(Not tracked)

Thunderbird 55.0


(Reporter: jorgk-bmo, Assigned: frg)


(Blocks 1 open bug)


(Whiteboard: [Thunderbird-testfailure: X Linux, Win])


(1 file)

TEST-UNEXPECTED-FAIL | toolkit/components/crashes/tests/xpcshell/test_crash_service.js | xpcshell return code: 0
TEST-UNEXPECTED-FAIL | toolkit/components/crashes/tests/xpcshell/test_crash_service.js | test_addCrash - [test_addCrash : 59] "undefined" == "content"

First seen on Daily run on Thu Jun 1, 2017, 16:59:46

M-C: last good: 0bcea6bac1797e14b00af45cc7c368d124
M-C: first bad: aeb3d0ca558f034cbef1c5a68bd07dd738


14:09:44  WARNING -  TEST-UNEXPECTED-FAIL | toolkit/components/crashes/tests/xpcshell/test_crash_service.js | test_addCrash - [test_addCrash : 59] "undefined" == "content"
14:09:44     INFO -  C:/slave/test/build/tests/xpcshell/tests/toolkit/components/crashes/tests/xpcshell/test_crash_service.js:test_addCrash:59
14:09:44     INFO -  exiting test
14:09:44     INFO -  Unexpected exception 2147500036
14:09:44     INFO -  undefined
14:09:44     INFO -  exiting test
14:09:44     INFO -  PID 6544 | JavaScript error: resource://gre/modules/XPCOMUtils.jsm, line 230: uncaught exception: 2147500037
14:09:44     INFO -  "CONSOLE_MESSAGE: (error) [JavaScript Error: "uncaught exception: 2147500037" {file: "resource://gre/modules/XPCOMUtils.jsm" line: 230}]"
14:09:44     INFO -  PID 6544 | Unable to read VR Path Registry from C:\\Users\\cltbld.T-W732-IX-061.002\\AppData\\Local\\openvr\\openvrpaths.vrpath

2147500037 = 0x80004005 = NS_ERROR_FAILURE

This comes from bug 1359326:
since test_addCrash is now failing.

Gabriele and Benjamin: Any hints why this test is now failing in the Thunderbird Xpcshell suite which is running the Mozilla core tests?

Apparently this line is failing:
59  Assert.equal(crash.metadata.ProcessType, "content");

An interesting aspect is that the test is only failing on Linux and Windows, not failing on Mac.
Flags: needinfo?(gsvelto)
Flags: needinfo?(benjamin)
This test extracts information from a dummy crash file. The annotation that is missing and is causing the test to fail is extracted here:

If we don't reach that part of the code it means that the previous line in which we run the minidump-analyzer tool failed. The minidump-analyzer normally lives in the dist/bin directory when running tests and it's located by looking for it in the "GreBinD" directory obtained by the directory service, see here:

If this is failing only on Linux and Windows but not on Mac then chances are that the code cannot find the minidump-analyzer executable on those two platforms but finds it successfully on Mac. I don't have a comm-central build handy to check what's happening but I'll be glad to help on fixing this.
Flags: needinfo?(gsvelto)
Flags: needinfo?(benjamin)
Bug 1317968 adds it to the distribution. Does this need porting?
(In reply to Frank-Rainer Grahl (:frg) from comment #2)
> Bug 1317968 adds it to the distribution. Does this need porting?

If you want to get stack traces in crash pings from release versions then yes. If not then I can amend the crash service code (and tests) to ignore failures if the minidump-analyzer is not present.
Tested with suite. Seems to be build but not distributed for OSX.
Attachment #8874473 - Flags: review?(jorgk)
Ahh I see. It is in BINPATH@/

So that is why OSX does not fail. I think I can safely take the bug now :)
Assignee: nobody → frgrahl
Comment on attachment 8874473 [details] [diff] [review]

Thanks, let me land this with bug 1370302. (Sorry out for Pfingsten.)
Attachment #8874473 - Flags: review?(jorgk) → review+
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 55.0
Blocks: 1370314
You need to log in before you can comment on or make changes to this bug.