Closed
Bug 773703
Opened 12 years ago
Closed 7 years ago
on B2G xpcshell always returns 1
Categories
(Core :: XPConnect, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mihneadb, Unassigned)
Details
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.
Comment 1•12 years ago
|
||
If this is actually a bug in the xpcshell binary, then the right component is Core:XPConnect.
Updated•12 years ago
|
Component: XPCShell Harness → XPConnect
Product: Testing → Core
Comment 2•12 years ago
|
||
We've verified that xpcshell always exits with a return code of 1 on B2G, even after successfully running tests.
Comment 3•12 years ago
|
||
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.
Comment 4•12 years ago
|
||
We see the same thing when running on Android devices: see bug 768491.
Reporter | ||
Comment 5•12 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?
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•