This is the case on opt builds, but at least on tbpl, debug builds of
xpcshell dump error information about why a file failed to load/run,
e.g.
https://tbpl.mozilla.org/php/getParsedLog.php?id=43053178&tree=Mozilla-Esr24
~ Gijs
On 11/07/2014 09:12, Mike de Boer wrote:
Error code 3, for me, always meant that I made a typo in head.js - or other JS
files loaded other than the test file itself - that caused a SyntaxError.
It’s unfortunate that there’s no better error reporting during loading and
evaluation of JS while loading the harness, so I needed to resort to
printf-debugging (`dump(“1.\n”); … dump(“2.\n”);` etc) to figure out where
things went wrong. When I narrowed it down close enough, I wrapped the
suspicious code in a try…catch block and dumped the exception message- and
stack-properties.
I hope this helps!
Mike.
On 11 Jul 2014, at 04:51, Yonggang Luo <luoyongg...@gmail.com> wrote:
Thanks, I found the files, but when I running unittest, I have the error code 3
for all test cases.
I'd like to know what's the possible reason to cause this.
On 7/10/14, 6:54 PM, Yonggang Luo wrote:
I found following code in `runxpcshelltests.py`:
def buildXpcsRunArgs(self):
"""
Add arguments to run the test or make it interactive.
"""
if self.interactive:
self.xpcsRunArgs = [
'-e', 'print("To start the test, type |_execute_test();|.");',
'-i']
else:
self.xpcsRunArgs = ['-e', '_execute_test(); quit(0);']
But I don't know where does _execute_test() comes from.
testing/xpcshell/head.js is contains all the code for setting up and
running each individual xpcshell test. _execute_test() lives in that file.
https://hg.mozilla.org/mozilla-central/file/e1a037c085d1/testing/xpcshell/head.js#l375
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
