The default bug view has changed. See this FAQ.

on B2G xpcshell always returns 1

NEW
Unassigned

Status

()

Core
XPConnect
5 years ago
5 years ago

People

(Reporter: mihneadb, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
Running the XPCShell tests on B2G, every test suite shows that "test failed; xpcshell exited with return code 1; see following log:" and the log that follows only contains "test-pass" and "test-info". So for some reason it returns 1 even when everything is OK.
If this is actually a bug in the xpcshell binary, then the right component is Core:XPConnect.
Component: XPCShell Harness → XPConnect
Product: Testing → Core
We've verified that xpcshell always exits with a return code of 1 on B2G, even after successfully running tests.
I mostly meant that you should try running xpcshell itself without the test harness and see if the behavior reproduces. If so then it's certainly a bug in the xpcshell binary. If not, then it might just be a harness bug.
We see the same thing when running on Android devices: see bug 768491.
(Reporter)

Comment 5

5 years ago
(In reply to Ted Mielczarek [:ted] from comment #3)
> I mostly meant that you should try running xpcshell itself without the test
> harness and see if the behavior reproduces. If so then it's certainly a bug
> in the xpcshell binary. If not, then it might just be a harness bug.

http://pastebin.mozilla.org/1702951

Weird return codes everytime. Also, it might be that the get_return_code logic (which basically runs echo $? and parses that) truncates it to only the first digit and get the 1 from thre?
You need to log in before you can comment on or make changes to this bug.