On 2014-10-02, 4:40 PM, Mike de Boer wrote:
Thanks for bringing this up!
So ever since extra super awesome strict warning were turned on we indeed have
to endure longer tail logs during test runs and when running debug builds. Just
like I get the information telling me which video card my computer has for
about the 1000th time.
All in all, for someone looking for it, enough source for frustration! Now that
we got past that point, let’s try to solve this!
So how about starting with a tool that scrapes the warnings from the tbpl logs?
I’m thinking it might be a cool Treeherder plugin. We got logs filenames and
line numbers, a vcs, so we can even run a blame command and auto-create bugs
and and auto-assign them to the one who introduced the error (or at least knows
more about it)…
Most of the errors I usually see are about uninitialised variables and
undefined properties. JS errors are very bad. If they’re expected for some
reason, it’d at least be nice to put a try…catch block around it to suppress
the log clutter.
These are all _very_ easy to fix.
I think a tool would help greatly.
Are we going to spend the time to fix these, however? For context, for
as long as I remember, if you kept the browser console open and used the
browser, we'd occasionally report an unhandled chrome JS errors (for
example when attempting to access properties off of null variables).
And those are not even strict errors.
I've occasionally filed bugs for them, but my impression was that unless
I can construct a case for those warnings to map to a user visible bug,
they would not be fixed.
_______________________________________________
dev-platform mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-platform
