Re: Some recent crash-stats improvements

2016-10-11 Thread Sebastian Zartner 
On 11 October 2016 at 05:41, Nicholas Nethercote 
wrote:

> On Tue, Oct 11, 2016 at 5:17 AM, Peter Bengtsson 
> wrote:
> >
> > If indeed, the memory report is safe to always show I'll change the
> template
> > to always show the memory_report link (if applicable).
> >
> > Nicholas?
>
> Based on nothing more than gut feeling, I'd prefer to keep it as PII.
> Just feels like the right thing to do...
>

Then the message should at least be adjusted to mention that you need
special permissions to download the reports (and where to ask for them) to
avoid confusion.

Sebastian
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Some recent crash-stats improvements

2016-10-10 Thread Nicholas Nethercote 
On Tue, Oct 11, 2016 at 5:17 AM, Peter Bengtsson  wrote:
>
> If indeed, the memory report is safe to always show I'll change the template
> to always show the memory_report link (if applicable).
>
> Nicholas?

Based on nothing more than gut feeling, I'd prefer to keep it as PII.
Just feels like the right thing to do...

Nick
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Some recent crash-stats improvements

2016-10-10 Thread Peter Bengtsson 
On Mon, Oct 10, 2016 at 1:42 PM, Eric Rahm  wrote:

> Is there a reason you need permissions for the memory report? Don't we
> anonymize it?
>
>
The link was made private when we thought it did contain possible PII.
Spoke to Ted about it.
He prefers to defer the fact finding to Nicholas.

If indeed, the memory report is safe to always show I'll change the
template to always show the memory_report link (if applicable).

Nicholas?



> -e
>
> On Mon, Oct 10, 2016 at 8:34 AM, Benjamin Smedberg 
> wrote:
>
>> Yes, downloading raw minidumps and memory reports requires the PII
>> permission in crash-stats. This can be obtained by Mozilla employees with
>> the assent of your manager, although I'm not sure now what the correct
>> bugzilla component is.
>>
>> --BDS
>>
>> On Mon, Oct 10, 2016 at 6:23 PM, Ben Kelly  wrote:
>>
>> > Does the "raw dump" tab support require special permissions?  I don't
>> see
>> > any way to download the memory report from:
>> >
>> > https://crash-stats.mozilla.com/report/index/1a572047-
>> > ac64-4add-a82f-a31512161004#tab-rawdump
>> >
>> > On Sun, Oct 9, 2016 at 7:51 PM, Nicholas Nethercote <
>> > n.netherc...@gmail.com>
>> > wrote:
>> >
>> > > Greetings,
>> > >
>> > > crash-stats.mozilla.org has had some recent improvements that are
>> > > worth highlighting.
>> > >
>> > > - There is new documentation on how to search through crash reports:
>> > > https://developer.mozilla.org/en-US/docs/A_guide_to_
>> > > searching_crash_reports.
>> > > You might think you already know how to do this, but crash-stats'
>> > > functionality for *grouping* search results is powerful and easy to
>> > > overlook, so this page is worth reading to make sure you understand it
>> > > fully. This documentation is linked to from the Super Search page
>> > > within crash-stats.
>> > >
>> > > - Some crash reports contain memory reports. (The
>> > > "ContainsMemoryReport" field is set in that case.) It used to be
>> > > difficult to download this memory report, but thanks to Peter
>> > > Bengtsson it's now much easier -- when a memory report is present,
>> > > there's now a link to it from the "Raw Dump" tab of an individual
>> > > crash report. See
>> > > https://crash-stats.mozilla.com/report/index/1a572047-
>> > > ac64-4add-a82f-a31512161004#tab-rawdump
>> > > for an example.
>> > >
>> > > - Also, something that is not in crash-stats but is closely related:
>> > > Marco Castellucio's new crash tools at
>> > > https://mozilla.github.io/stab-crashes/. There are several tools, but
>> > > probably the most widely-applicable one is
>> > > https://mozilla.github.io/stab-crashes/correlations.html, which finds
>> > > correlations for a particular crash signature. It works much better
>> > > than the existing correlations tool within crash-stats. If you have a
>> > > crash for which the cause is not obvious, this tool can be enormously
>> > > helpful -- e.g. bug 1307029 is for a generic-looking crash signature
>> > > that turns out to be highly correlated with a particular extension.
>> > >
>> > > Nick
>> > > ___
>> > > dev-platform mailing list
>> > > dev-platform@lists.mozilla.org
>> > > https://lists.mozilla.org/listinfo/dev-platform
>> > >
>> > ___
>> > dev-platform mailing list
>> > dev-platform@lists.mozilla.org
>> > https://lists.mozilla.org/listinfo/dev-platform
>> >
>> ___
>> dev-platform mailing list
>> dev-platform@lists.mozilla.org
>> https://lists.mozilla.org/listinfo/dev-platform
>>
>
>
> ___
> Stability mailing list
> stabil...@mozilla.org
> https://mail.mozilla.org/listinfo/stability
>
>


-- 
Peter Bengtsson
Mozilla Tools & Services
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Some recent crash-stats improvements

2016-10-10 Thread Eric Rahm 
Is there a reason you need permissions for the memory report? Don't we
anonymize it?

-e

On Mon, Oct 10, 2016 at 8:34 AM, Benjamin Smedberg 
wrote:

> Yes, downloading raw minidumps and memory reports requires the PII
> permission in crash-stats. This can be obtained by Mozilla employees with
> the assent of your manager, although I'm not sure now what the correct
> bugzilla component is.
>
> --BDS
>
> On Mon, Oct 10, 2016 at 6:23 PM, Ben Kelly  wrote:
>
> > Does the "raw dump" tab support require special permissions?  I don't see
> > any way to download the memory report from:
> >
> > https://crash-stats.mozilla.com/report/index/1a572047-
> > ac64-4add-a82f-a31512161004#tab-rawdump
> >
> > On Sun, Oct 9, 2016 at 7:51 PM, Nicholas Nethercote <
> > n.netherc...@gmail.com>
> > wrote:
> >
> > > Greetings,
> > >
> > > crash-stats.mozilla.org has had some recent improvements that are
> > > worth highlighting.
> > >
> > > - There is new documentation on how to search through crash reports:
> > > https://developer.mozilla.org/en-US/docs/A_guide_to_
> > > searching_crash_reports.
> > > You might think you already know how to do this, but crash-stats'
> > > functionality for *grouping* search results is powerful and easy to
> > > overlook, so this page is worth reading to make sure you understand it
> > > fully. This documentation is linked to from the Super Search page
> > > within crash-stats.
> > >
> > > - Some crash reports contain memory reports. (The
> > > "ContainsMemoryReport" field is set in that case.) It used to be
> > > difficult to download this memory report, but thanks to Peter
> > > Bengtsson it's now much easier -- when a memory report is present,
> > > there's now a link to it from the "Raw Dump" tab of an individual
> > > crash report. See
> > > https://crash-stats.mozilla.com/report/index/1a572047-
> > > ac64-4add-a82f-a31512161004#tab-rawdump
> > > for an example.
> > >
> > > - Also, something that is not in crash-stats but is closely related:
> > > Marco Castellucio's new crash tools at
> > > https://mozilla.github.io/stab-crashes/. There are several tools, but
> > > probably the most widely-applicable one is
> > > https://mozilla.github.io/stab-crashes/correlations.html, which finds
> > > correlations for a particular crash signature. It works much better
> > > than the existing correlations tool within crash-stats. If you have a
> > > crash for which the cause is not obvious, this tool can be enormously
> > > helpful -- e.g. bug 1307029 is for a generic-looking crash signature
> > > that turns out to be highly correlated with a particular extension.
> > >
> > > Nick
> > > ___
> > > dev-platform mailing list
> > > dev-platform@lists.mozilla.org
> > > https://lists.mozilla.org/listinfo/dev-platform
> > >
> > ___
> > dev-platform mailing list
> > dev-platform@lists.mozilla.org
> > https://lists.mozilla.org/listinfo/dev-platform
> >
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Some recent crash-stats improvements

2016-10-10 Thread Kevin Brosnan 
It does. You need to file a bug like
https://bugzilla.mozilla.org/show_bug.cgi?id=1118990

Kevin Brosnan

On Mon, Oct 10, 2016 at 8:23 AM, Ben Kelly  wrote:

> Does the "raw dump" tab support require special permissions?  I don't see
> any way to download the memory report from:
>
> https://crash-stats.mozilla.com/report/index/1a572047-
> ac64-4add-a82f-a31512161004#tab-rawdump
>
> On Sun, Oct 9, 2016 at 7:51 PM, Nicholas Nethercote <
> n.netherc...@gmail.com>
> wrote:
>
> > Greetings,
> >
> > crash-stats.mozilla.org has had some recent improvements that are
> > worth highlighting.
> >
> > - There is new documentation on how to search through crash reports:
> > https://developer.mozilla.org/en-US/docs/A_guide_to_
> > searching_crash_reports.
> > You might think you already know how to do this, but crash-stats'
> > functionality for *grouping* search results is powerful and easy to
> > overlook, so this page is worth reading to make sure you understand it
> > fully. This documentation is linked to from the Super Search page
> > within crash-stats.
> >
> > - Some crash reports contain memory reports. (The
> > "ContainsMemoryReport" field is set in that case.) It used to be
> > difficult to download this memory report, but thanks to Peter
> > Bengtsson it's now much easier -- when a memory report is present,
> > there's now a link to it from the "Raw Dump" tab of an individual
> > crash report. See
> > https://crash-stats.mozilla.com/report/index/1a572047-
> > ac64-4add-a82f-a31512161004#tab-rawdump
> > for an example.
> >
> > - Also, something that is not in crash-stats but is closely related:
> > Marco Castellucio's new crash tools at
> > https://mozilla.github.io/stab-crashes/. There are several tools, but
> > probably the most widely-applicable one is
> > https://mozilla.github.io/stab-crashes/correlations.html, which finds
> > correlations for a particular crash signature. It works much better
> > than the existing correlations tool within crash-stats. If you have a
> > crash for which the cause is not obvious, this tool can be enormously
> > helpful -- e.g. bug 1307029 is for a generic-looking crash signature
> > that turns out to be highly correlated with a particular extension.
> >
> > Nick
> > ___
> > dev-platform mailing list
> > dev-platform@lists.mozilla.org
> > https://lists.mozilla.org/listinfo/dev-platform
> >
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Some recent crash-stats improvements

2016-10-10 Thread Benjamin Smedberg 
Yes, downloading raw minidumps and memory reports requires the PII
permission in crash-stats. This can be obtained by Mozilla employees with
the assent of your manager, although I'm not sure now what the correct
bugzilla component is.

--BDS

On Mon, Oct 10, 2016 at 6:23 PM, Ben Kelly  wrote:

> Does the "raw dump" tab support require special permissions?  I don't see
> any way to download the memory report from:
>
> https://crash-stats.mozilla.com/report/index/1a572047-
> ac64-4add-a82f-a31512161004#tab-rawdump
>
> On Sun, Oct 9, 2016 at 7:51 PM, Nicholas Nethercote <
> n.netherc...@gmail.com>
> wrote:
>
> > Greetings,
> >
> > crash-stats.mozilla.org has had some recent improvements that are
> > worth highlighting.
> >
> > - There is new documentation on how to search through crash reports:
> > https://developer.mozilla.org/en-US/docs/A_guide_to_
> > searching_crash_reports.
> > You might think you already know how to do this, but crash-stats'
> > functionality for *grouping* search results is powerful and easy to
> > overlook, so this page is worth reading to make sure you understand it
> > fully. This documentation is linked to from the Super Search page
> > within crash-stats.
> >
> > - Some crash reports contain memory reports. (The
> > "ContainsMemoryReport" field is set in that case.) It used to be
> > difficult to download this memory report, but thanks to Peter
> > Bengtsson it's now much easier -- when a memory report is present,
> > there's now a link to it from the "Raw Dump" tab of an individual
> > crash report. See
> > https://crash-stats.mozilla.com/report/index/1a572047-
> > ac64-4add-a82f-a31512161004#tab-rawdump
> > for an example.
> >
> > - Also, something that is not in crash-stats but is closely related:
> > Marco Castellucio's new crash tools at
> > https://mozilla.github.io/stab-crashes/. There are several tools, but
> > probably the most widely-applicable one is
> > https://mozilla.github.io/stab-crashes/correlations.html, which finds
> > correlations for a particular crash signature. It works much better
> > than the existing correlations tool within crash-stats. If you have a
> > crash for which the cause is not obvious, this tool can be enormously
> > helpful -- e.g. bug 1307029 is for a generic-looking crash signature
> > that turns out to be highly correlated with a particular extension.
> >
> > Nick
> > ___
> > dev-platform mailing list
> > dev-platform@lists.mozilla.org
> > https://lists.mozilla.org/listinfo/dev-platform
> >
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Some recent crash-stats improvements

2016-10-10 Thread Ben Kelly 
Does the "raw dump" tab support require special permissions?  I don't see
any way to download the memory report from:

https://crash-stats.mozilla.com/report/index/1a572047-ac64-4add-a82f-a31512161004#tab-rawdump

On Sun, Oct 9, 2016 at 7:51 PM, Nicholas Nethercote 
wrote:

> Greetings,
>
> crash-stats.mozilla.org has had some recent improvements that are
> worth highlighting.
>
> - There is new documentation on how to search through crash reports:
> https://developer.mozilla.org/en-US/docs/A_guide_to_
> searching_crash_reports.
> You might think you already know how to do this, but crash-stats'
> functionality for *grouping* search results is powerful and easy to
> overlook, so this page is worth reading to make sure you understand it
> fully. This documentation is linked to from the Super Search page
> within crash-stats.
>
> - Some crash reports contain memory reports. (The
> "ContainsMemoryReport" field is set in that case.) It used to be
> difficult to download this memory report, but thanks to Peter
> Bengtsson it's now much easier -- when a memory report is present,
> there's now a link to it from the "Raw Dump" tab of an individual
> crash report. See
> https://crash-stats.mozilla.com/report/index/1a572047-
> ac64-4add-a82f-a31512161004#tab-rawdump
> for an example.
>
> - Also, something that is not in crash-stats but is closely related:
> Marco Castellucio's new crash tools at
> https://mozilla.github.io/stab-crashes/. There are several tools, but
> probably the most widely-applicable one is
> https://mozilla.github.io/stab-crashes/correlations.html, which finds
> correlations for a particular crash signature. It works much better
> than the existing correlations tool within crash-stats. If you have a
> crash for which the cause is not obvious, this tool can be enormously
> helpful -- e.g. bug 1307029 is for a generic-looking crash signature
> that turns out to be highly correlated with a particular extension.
>
> Nick
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform