I think yes, yes and yes! Although for 2) I think we can break it down
into a priority of startup where modules are initialised, these seem to
point to configuration issues/regressions like the ril ones that Kevin
has addressed lately.
The only preference I have is that I would like them to be caught and
reported independently of functional tests.
If we try to catch them incidentally during functional tests it won't be
reliable and repeatable due to timing variations and its a risk of the
exception failure being misinterpreted as a functional/test failure.
Functional tests seem like a good place to piggyback on because they
cover a lot of UI journeys but this kind of misinterpretation is real,
we suffer it already on gaia-ui-tests.
Unless you can be 100% sure of the relationship between the function and
the error message.
Zac
On 15/01/14 04:11, 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
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
