Re: How does xpcshell unittest are runned

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, a

Re: How does xpcshell unittest are runned

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

Re: How does xpcshell unittest are runned

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 buildXpcsRunArg

Re: How does xpcshell unittest are runned

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',

How does xpcshell unittest are runned

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();