Indeed, which is why I recommended "assert", not "warn".
Warnings are basically useless from a CI standpoint. If you want to guarantee it, don't warn, assert. -Jeff ----- Original Message ----- From: "Martin Thomson" <m...@mozilla.com> To: dev-platform@lists.mozilla.org Sent: Thursday, October 2, 2014 1:05:44 PM Subject: Re: JavaScript (strict) Warning from FF mochitest-plain test. On 02/10/14 12:52, Chris Peterson wrote: > SpiderMonkey already forces ES5 strict mode and "extra warnings" mode > for all self-hosted JS: bug 784295. The problem is that this only generates an exception, not a test failure, so if the error is in code that isn't depended upon (also a problem), then it just disappears. _______________________________________________ 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