754851 - JS Errors in mozmill modules are not shown on the command line

Status: RESOLVED WONTFIX

(Testing Graveyard :: Mozmill, defect)

Description

[Henrik Skupin [:whimboo][⌚️UTC+2] (away 07/21 - 08/08)]

If an exception is thrown in a securable module, e.g components/driver.js by redefining Cc at the top of the file, no error is shown in the console. This makes it nearly impossible to figure out the real failure. This has to be fixed before we can consider bug 754849 to be implemented.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2] (away 07/21 - 08/08)]

This doesn't only happen for securable modules but also if you make some code invalid in mozmill.js. I can see errors in the Error Console but those are not reported via JSBridge. I think that should block.

Comment 2

[cmtalbert]

So I don't know how this worked in 1.5.x, but in 2.0 we have changed to use our msg broker and console service listener.  If any of our modules crash in this way such that a top level exception is thrown from a *mozmill module* then the entire system crashes and you don't get anything coming back to the log, ever.  (Because the code that would have originally mirrored such a failure to the stdout has itself been destroyed).

So, there's not really anything we can do here.

I verified that javascript exceptions in tests or modules that tests load *DO* get mirrored out to the log, which is really the more important case.

So, going to have to WONTFIX this. :(