1218528 - [e10s] Provide a way to filter Socorro top crash tables based on DOMIPCEnabled annotation

Status: RESOLVED WORKSFORME

(Socorro :: General, task)

Description

[Erin Lancaster [:elan]]

Will move to correct component as soon as I figure it out. :)

Comment 1

[Peter Bengtsson [:peterbe]]

uh!? When I added myself to this bug (simply by hitting Save Changes) it unset your "tracking-e10s" flag. 
I don't have that as an option: https://www.dropbox.com/s/aff0ipvevgw0r6z/Screenshot%202015-10-27%2015.06.56.png?dl=0 sorry

Comment 2

[Robert Kaiser]

The standard crash rate cannot be available for e10s vs. non-e10s and we can't fix it without a real lot of work. It depends on ADI which are completely unaware of things like the e10s pref.

I want us to get some crash rates (which will be heavily incompatible with the current and historic ones) out of Unified Telemetry, but I haven't looked at any details on that. Doing that is also completely outside of what Socorro does or should do.

Comment 3

[Jim Mathies [:jimm]]

> I want us to get some crash rates (which will be heavily incompatible with
> the current and historic ones) out of Unified Telemetry, but I haven't
> looked at any details on that. Doing that is also completely outside of what
> Socorro does or should do.

This is covered by bug 1198842.

Comment 4

[Jim Mathies [:jimm]]

I missed the meeting where this was set up. Erin, what did we want here? In the original rc discussions it was noted that crashstats data would not be used to track stability. We would instead use telemetry pings for this, hence bug 1198842. Should we dupe this over to that bug and get it tracked under this beta tracker?

Comment 5

[Erin Lancaster [:elan]]

I checked with bsmedberg, here is some clarity: 
(1)We're going to measure crash *rates* using telemetry and not crash-stats
(2)Crash-stats still needs work so that we can generate separate lists of topcrashes by e10s and non-e10s

Laura has been kind enough to have us work with Peter on this. NI so he can chime in.

Comment 6

[[DEACTIVATED] Adrian Gaudebert]

Here's how you can see crashes that have DOMIPCEnabled as true using Super Search: 

https://crash-stats.mozilla.com/search/?product=Firefox&dom_ipc_enabled=!__null__

In the UI it translates to `dom ipc enabled` `exists`. Use `does not exist` for crashes that do not have DOMIPCEnabled. 

Please note that this filter will work only in Super Search based pages, so only Super Search and Signature report. Going to report/list/ for example will lose that filter, as it is not supported there.

Comment 7

[Peter Bengtsson [:peterbe]]

I believe Adrian has demonstrated that you can user Super Search to query on dom_ipc_enabled on and off.

Comment 8

[Robert Kaiser]

Yes, we just need to do a search, and that's fine, that all we should do and need.

That said, as long as we know that e10s make overall crash rates worse by a significant degree (which is currently true on 43 as we know from dev edition), I have to veto it being on for *anyone* at least in the last 3 weeks of the beta cycle because I have to work with historical views of ADI-based crash rates to determine if what we have in betas is good enough for release.

Comment 9

[Jim Mathies [:jimm]]

Thanks guys. I had a feeling we could pull this up within the existing interface.