761905 - (b2g-crash-reporting) Tracking: Crash reporting for b2g (gonk)

Status: RESOLVED WONTFIX

(Toolkit :: Crash Reporting, defect)

Comment 1

[Dietrich Ayala (:dietrich)]

Ted, Robert: Do the dependent bugs here represent the totality of work required for end-to-end B2G crash reporting support?

Comment 2

[(not currently active) Ted Mielczarek]

I just filed two more bugs about things we had discussed that never got filed. I can't think of anything else that's required to make this work. Socorro-side there shouldn't be any changes necessary, unless we add some annotations in bug 777187 that we want exposed.

Comment 3

[Robert Kaiser]

Barring any new annotations, bug 774290 should probably be the only thing on the Socorro side that we need (and that one is pretty simple), at least for getting some kind of support.
For having permanent and really good support, some tuning in reaction to release mechanics could be needed (depending on how that process will work for B2G) and we only can get crash *rates* (crashes/ADU) is we have ADU data or something similar.
Being perfect is probably not really in scope for v1, though. ;-)

Comment 4

[Robert Kaiser]

The UI for crash reporting is being tracked on GitHub, BTW: https://github.com/mozilla-b2g/gaia/issues/4149

Comment 5

[Benoit Jacob [:bjacob] (mostly away)]

bug 811483 may be of interest if you wonder which crashes are OOM.

Comment 6

[Sylvestre Ledru [:Sylvestre]]

Mass closing as we are no longer working on b2g/firefox os.

Comment 7

[Sylvestre Ledru [:Sylvestre]]

Mass closing as we are no longer working on b2g/firefox os.