The feedback to this proposal is overwhelmingly positive, so we'll try
and get something stood up, possibly on a project branch or possibly
just printing warnings to the summary instead of causing an outright job
failure for now. We'll need to fix all of the currently existing
exceptions before we can start failing jobs based on these errors.
I think we'll focus on JS errors for now, we can always look into adding
css problems in the future.
On 15/01/14 12:11 PM, Andrew Halberstadt wrote:
Many of you may have noticed that when using b2g desktop or the
emulator, the logcat is riddled with Javascript exceptions from various
apps and parts of the platform. For example, search [1] for "JavaScript
error". While many of these errors may generally be harmless, it is not
possible to tell for sure. They also make it much harder to determine
points of failure.
In bug 959493 [2] we are discussing flagging these types of errors as
failures in TBPL. This proposal would mean that any checkin (in either
gaia or gecko) causing such an exception would be backed out. There are
a few questions I'd like to ask you:
1) Is this a good idea?
2) Should we only look at startup failures or for example all failures
throughout an entire mochitest run?
3) If a test run modifies the profile, does that disqualify it from
having the check turned on?
Thanks for your input,
Andrew
[1]
https://tbpl.mozilla.org/php/getParsedLog.php?id=32961324&tree=Cypress&full=1
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=959493
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
