Awesome, this sounds like what I was after. (though actual components isn't really necessary. If that part is a pain point, I would prefer to have a tool without it, than to have no tool)
On Wed, Jun 1, 2016 at 12:23 PM, Ted Mielczarek <t...@mielczarek.org> wrote: > On Tue, May 31, 2016, at 09:26 PM, Jeff Gilbert wrote: >> On Tue, May 31, 2016 at 4:39 PM, Nicholas Nethercote >> <n.netherc...@gmail.com> wrote: >> > On Wed, Jun 1, 2016 at 1:05 AM, Benjamin Smedberg <benja...@smedbergs.us> >> > wrote: >> >> You shouldn't need to annotate the file/line separately, because that is >> >> (or at least should be!) the top of the stack. >> > >> > Yes. Don't get hung up on the lack of annotations. It isn't much of a >> > problem; you can click through easily enough. I have filed bug 1277104 >> > to fix the handful of instances that are showing up in practice, but >> > it'll only be a minor improvement. >> >> Perhaps this isn't meant for me then? I looked at the query from the >> first post, but it's just noise to me. If it included the file that it >> crashed from, it would suddenly be very useful, since it'd then be >> trivial to see if there's something relevant to me. >> >> As it stands now, the query alone doesn't seem useful to me. If it's >> meant to be useful to developers who write MOZ_CRASHes, this is a >> problem. If not, please ignore! >> >> I would be extremely interested in MOZ_CRASHes and friends >> automatically getting bugs filed and needinfo'd. An index of >> crashes-by-file would get half-way there for me. > > I believe at some point in the past we talked about trying to do a "top > crashes by bug component" view, but maintaining that mapping was hard. > It turns out that we're storing this data in moz.build files nowadays > (for example[1]), and we even have a web service on hg.mozilla.org to > expose it for any given revision[2]. Unfortunately that web service is > currently broken[3], but gps tells me he's just been delaying fixing it > because there weren't any consumers complaining. > > When the source file from the last frame of the stack used to generate > the signature points to hg.mozilla.org we could query that web service > to get a bug component for the file in question and put that in the > crash report, and expose it to queries. That would make it easy to get > lists of crashes by component, which I think would do what people here > are asking for. I filed bug 1277337 to track this idea. > > -Ted > > 1. > https://dxr.mozilla.org/mozilla-central/rev/4d63dde701b47b8661ab7990f197b6b60e543839/dom/media/moz.build#7 > 2. > http://mozilla-version-control-tools.readthedocs.io/en/latest/hgmo/mozbuildinfo.html > 3. https://bugzilla.mozilla.org/show_bug.cgi?id=1263973 > 4. https://bugzilla.mozilla.org/show_bug.cgi?id=1277337 _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
