<div dir="ltr"><div>It would be great to default to public repos (except where there is a specific reason not to).<br></div><div>I think we should keep up with the openness we have at Mozilla; for reasons of transparency, contributor/community access, knowledge sharing... and even ease of team access.<br><br></div><div>Georg<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 28, 2017 at 9:29 PM, Saptarshi Guha <span dir="ltr"><<a href="mailto:sguha@mozilla.com" target="_blank">sguha@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace">Aah, it's private. Will make it public or give you access</div><div class="gmail_default" style="font-family:monospace,monospace">Cheers</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 28, 2017 at 12:26 PM, Chris Hutten-Czapski <span dir="ltr"><<a href="mailto:chutten@mozilla.com" target="_blank">chutten@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Ack, 404.<br></div><div class="m_7456695367343958022HOEnZb"><div class="m_7456695367343958022h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 28, 2017 at 3:25 PM, Saptarshi Guha <span dir="ltr"><<a href="mailto:sguha@mozilla.com" target="_blank">sguha@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace">Absolutely. </div><div class="gmail_default" style="font-family:monospace,monospace">Github: <a href="https://github.com/aguimaraesduarte/CrashGraphs" target="_blank">https://github.com/agu<wbr>imaraesduarte/CrashGraphs</a></div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">I'll schedule a meeting with Andre,Connor,Chris and myself to discuss the inner workings of this.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">Cheers</div><span class="m_7456695367343958022m_5913559150387580819HOEnZb"><font color="#888888"><div class="gmail_default" style="font-family:monospace,monospace">Saptarshi</div></font></span></div><div class="m_7456695367343958022m_5913559150387580819HOEnZb"><div class="m_7456695367343958022m_5913559150387580819h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 28, 2017 at 12:23 PM, Chris Hutten-Czapski <span dir="ltr"><<a href="mailto:chutten@mozilla.com" target="_blank">chutten@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>A better link for the telemetry-based crash measurements is
<a href="https://telemetry.mozilla.org/crashes/" target="_blank">https://telemetry.mozilla.org/<wbr>crashes/</a> (telemetry_crashes on my gh-pages
is now unmaintained)<br><br></div>Very nice, I like the layout and presentation.<br><br></div>Can we take a look at the analysis backing the data? Your page shows numbers that are very different from other measures of crashes per
kuh[1][2][3]. I think there are a couple of things that might contribute to
this, but without looking at the analysis itself I can only speculate. (and this is beyond the aforementioned content shutdownkill issue)<br></div><div><br></div>:chutten<br><div><br>[1]: <a href="https://telemetry.mozilla.org/crashes/" target="_blank">https://telemetry.mozilla.org/<wbr>crashes/</a><br>[2]: <a href="https://sql.telemetry.mozilla.org/dashboard/stability-metrics-for-e10s-add-ons-experiment-release-49-50-51-" target="_blank">https://sql.telemetry.mozilla.<wbr>org/dashboard/stability-metric<wbr>s-for-e10s-add-ons-experiment-<wbr>release-49-50-51-</a><br>[3]: <a href="https://sql.telemetry.mozilla.org/queries/689#1163" target="_blank">https://sql.telemetry.mozilla.<wbr>org/queries/689#1163</a><br><br></div></div><div class="m_7456695367343958022m_5913559150387580819m_-3044209741329962625HOEnZb"><div class="m_7456695367343958022m_5913559150387580819m_-3044209741329962625h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 28, 2017 at 3:18 PM, Saptarshi Guha <span dir="ltr"><<a href="mailto:sguha@mozilla.com" target="_blank">sguha@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace">Very very likely. As mentioned in the initial post</div><span><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">"</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:12.8px"><br class="m_7456695367343958022m_5913559150387580819m_-3044209741329962625m_4955045095781350172m_6619587562072982924gmail-Apple-interchange-newline">Also since we use main_summary, we cannot eliminate shutdown crashes. That would be a nice metric to include in main_summary itself.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:12.8px"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:12.8px">That said, on average shutdown crashes is a fairly constant fraction of total content crashes [1] (the latter measured in main_summary). That is on average. For a given profile with 5 content crashes(as per main_summary), it's tough to say how many are shutdown crashes</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:12.8px"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:12.8px">[1] <a href="https://docs.google.com/document/d/1jzcEPI4NLlar102kS1WBv1cgnxDULYQNl4VawmQEr5c/edit#heading=h.imxtnojofajm" target="_blank">https://docs.google.com/do<wbr>cument/d/1jzcEPI4NLlar102kS1WB<wbr>v1cgnxDULYQNl4VawmQEr5c/edit#h<wbr>eading=h.imxtnojofajm</a></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:12.8px"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:12.8px">"</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:12.8px"><br></div></span><div class="gmail_default" style="font-family:monospace,monospace;font-size:12.8px">We would love to remove shutdown crashes but since we use main-summary we cannot.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:12.8px"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:12.8px">crash_summary table might be a fix for this. Last i checked it didn't have some fields</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:12.8px">we need (for determining new users). If it has we can move to that and remove shutdowns</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:12.8px"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:12.8px">Thanks for the comment. This is increases the urgency to get fields we need into crashsummary</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:12.8px">( <a href="https://github.com/mozilla/telemetry-batch-view/blob/master/src/main/scala/com/mozilla/telemetry/views/CrashSummaryView.scala" target="_blank">https://github.com/mozilla/t<wbr>elemetry-batch-view/blob/maste<wbr>r/src/main/scala/com/mozilla/t<wbr>elemetry/views/CrashSummaryVie<wbr>w.scala</a> )</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:12.8px"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:12.8px"><br></div></div><div class="m_7456695367343958022m_5913559150387580819m_-3044209741329962625m_4955045095781350172HOEnZb"><div class="m_7456695367343958022m_5913559150387580819m_-3044209741329962625m_4955045095781350172h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 28, 2017 at 12:03 PM, Mike Conley <span dir="ltr"><<a href="mailto:mconley@mozilla.com" target="_blank">mconley@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I may not be sharing new information here (I just subscribed to this<br>
mailing list!), but thought I'd add in here:<br>
<br>
I do know that at least for e10s, there is a specific type of crash,<br>
("shutdownkill crashes") that occur silently, and on purpose. This is<br>
when the content process does not shut down in time. When that occurs,<br>
the parent process kills the content process and collects a minidump for<br>
submission. This happens without the crash reporter dialog being<br>
presented to the user.<br>
<br>
When evaluating e10s release criteria, I believe these crashes were<br>
subtracted from the overall content crash rate. You can see that in<br>
chutten's graph here:<br>
<br>
<a href="https://chutten.github.io/telemetry_crashes/" rel="noreferrer" target="_blank">https://chutten.github.io/tele<wbr>metry_crashes/</a><br>
<br>
"M + C - Content Shutdown (M+C-S)" reflects what I'm talking about here.<br>
<br>
Could it be that the 10x increase you're seeing is mostly composed of<br>
shutdownkill crashes?<br>
<br>
-Mike<br>
<span><br>
On 28/02/2017 2:46 PM, John Jensen wrote:<br>
> Congratulations for producing an information-filled, easy-to-digest<br>
> dashboard, but ....<br>
><br>
> Wow. Crash rates have increased 10x since September!?<br>
><br>
>> Content crashes have been steadily increasing since September 2016.<br>
>> Content crashes for profiles that have e10s enabled are significantly<br>
> higher (almost 20x) than for those that don't have it enabled,<br>
>> around 8-12% of weekly active Firefox users have experienced any type<br>
> of crash.<br>
>> The number of new profiles (created that week) that crashed is<br>
> increasing.<br>
>> The number of hours between crashes for users who have had a previous<br>
> crash in their history is decreasing. This means that crashes (of any<br>
> type) are becoming more frequent in general.<br>
>> Over 50% of Firefox users who crash per week have had their previous<br>
> crash within 7 days.<br>
><br>
> There is only alarming news on this dashboard. That's fine, but please<br>
> correct me if I am wrong.<br>
><br>
> I know it's not its objective, but are there better data<br>
> sources/analytic tools now to understand key drivers of these crashes?<br>
> Is there a dashboard, say, showing a "burndown" chart of fixes?<br>
><br>
> John<br>
><br>
><br>
><br>
><br>
> On 28 February 2017 at 11:23, Saptarshi Guha <<a href="mailto:sguha@mozilla.com" target="_blank">sguha@mozilla.com</a><br>
</span><div><div class="m_7456695367343958022m_5913559150387580819m_-3044209741329962625m_4955045095781350172m_6619587562072982924h5">> <mailto:<a href="mailto:sguha@mozilla.com" target="_blank">sguha@mozilla.com</a>>> wrote:<br>
><br>
> Happy to present the crashgraphs dashboard. A high level dashboard<br>
> that captures<br>
><br>
> - average profile crash rate (average across profiles crash rates)<br>
> - % of profiles crashing in the last week<br>
> - time between crashes for profiles that have another crash in their<br>
> history<br>
> (history is lifetime!)<br>
> - hours and days between crashes (for profiles with 2+ crashes).<br>
> Lower is *bad*<br>
><br>
> We capture two things i've been looking for<br>
><br>
> - a profile level view of crash (% of profiles experiencing a crash)<br>
> - a software engineering level view of crash (hours used across crashes)<br>
><br>
> This is high level so not as detailed as arwwestableyet.<br>
><br>
> Many thanks to Andre Duarte and Connor Ameres for working and<br>
> designing this.<br>
><br>
> Your comments welcome!<br>
><br>
> <a href="https://people-mozilla.org/~sguha/crashgraphs/" rel="noreferrer" target="_blank">https://people-mozilla.org/~s<wbr>guha/crashgraphs/</a><br>
> <<a href="https://people-mozilla.org/~sguha/crashgraphs/" rel="noreferrer" target="_blank">https://people-mozilla.org/~<wbr>sguha/crashgraphs/</a>><br>
><br>
> Regard<br>
> saptarsi<br>
><br>
><br>
> Appendix<br>
><br>
> Also since we use main_summary, we cannot eliminate shutdown<br>
> crashes. That would be a nice metric to include in main_summary itself.<br>
><br>
> That said, on average shutdown crashes is a fairly constant<br>
> fraction of total content crashes [1] (the latter measured in<br>
> main_summary). That is on average. For a given profile with 5<br>
> content crashes(as per main_summary), it's tough to say how many are<br>
> shutdown crashes<br>
><br>
> [1] <a href="https://docs.google.com/document/d/1jzcEPI4NLlar102kS1WBv1cgnxDULYQNl4VawmQEr5c/edit#heading=h.imxtnojofajm" rel="noreferrer" target="_blank">https://docs.google.com/docume<wbr>nt/d/1jzcEPI4NLlar102kS1WBv1cg<wbr>nxDULYQNl4VawmQEr5c/edit#headi<wbr>ng=h.imxtnojofajm</a><br>
> <<a href="https://docs.google.com/document/d/1jzcEPI4NLlar102kS1WBv1cgnxDULYQNl4VawmQEr5c/edit#heading=h.imxtnojofajm" rel="noreferrer" target="_blank">https://docs.google.com/docu<wbr>ment/d/1jzcEPI4NLlar102kS1WBv1<wbr>cgnxDULYQNl4VawmQEr5c/edit#hea<wbr>ding=h.imxtnojofajm</a>><br>
><br>
> _____________________________<wbr>__________________<br>
> fhr-dev mailing list<br>
</div></div>> <a href="mailto:fhr-dev@mozilla.org" target="_blank">fhr-dev@mozilla.org</a> <mailto:<a href="mailto:fhr-dev@mozilla.org" target="_blank">fhr-dev@mozilla.org</a>><br>
> <a href="https://mail.mozilla.org/listinfo/fhr-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/list<wbr>info/fhr-dev</a><br>
<span>> <<a href="https://mail.mozilla.org/listinfo/fhr-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/lis<wbr>tinfo/fhr-dev</a>><br>
><br>
><br>
><br>
><br>
> --<br>
> John Jensen<br>
</span>> <a href="mailto:jjensen@mozilla.com" target="_blank">jjensen@mozilla.com</a> <mailto:<a href="mailto:jjensen@mozilla.com" target="_blank">jjensen@mozilla.com</a>><br>
> Director, Organization Strategy<br>
<div class="m_7456695367343958022m_5913559150387580819m_-3044209741329962625m_4955045095781350172m_6619587562072982924HOEnZb"><div class="m_7456695367343958022m_5913559150387580819m_-3044209741329962625m_4955045095781350172m_6619587562072982924h5">><br>
><br>
> ______________________________<wbr>_________________<br>
> fhr-dev mailing list<br>
> <a href="mailto:fhr-dev@mozilla.org" target="_blank">fhr-dev@mozilla.org</a><br>
> <a href="https://mail.mozilla.org/listinfo/fhr-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi<wbr>nfo/fhr-dev</a><br>
><br>
______________________________<wbr>_________________<br>
fhr-dev mailing list<br>
<a href="mailto:fhr-dev@mozilla.org" target="_blank">fhr-dev@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/fhr-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi<wbr>nfo/fhr-dev</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
fhr-dev mailing list<br>
<a href="mailto:fhr-dev@mozilla.org" target="_blank">fhr-dev@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/fhr-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi<wbr>nfo/fhr-dev</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
fhr-dev mailing list<br>
<a href="mailto:fhr-dev@mozilla.org">fhr-dev@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/fhr-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/<wbr>listinfo/fhr-dev</a><br>
<br></blockquote></div><br></div>