Re: [Libreoffice-qa] organizing our "crasher" bugs ?

2015-05-28 Thread Alex Thurgood
Le 29/05/2015 04:07, Joel Madero a écrit : Hi Joel, > What I think would be minimum (and can be done) is: > Confirm each crash on 5.0; > _Ensure_ that each has easy steps; > > For the most straight forward ones that have easy steps we can just mark > them as critical + highest - signaling that

Re: [Libreoffice-qa] organizing our "crasher" bugs ?

2015-05-28 Thread Joel Madero
On 05/27/2015 07:25 AM, Caolán McNamara wrote: > There are ~190 bugs with the word "crash" in the summary in the states > new/assigned/reopened/unconfirmed. > > As with the coverity, import-testing, export-testing stuff I think it > would be helpful to start chewing into crashers in some systemat

Re: [Libreoffice-qa] organizing our "crasher" bugs ?

2015-05-27 Thread Terrence Enger
On Wed, 2015-05-27 at 15:25 +0100, Caolán McNamara wrote: > There are ~190 bugs with the word "crash" in the summary in the states > new/assigned/reopened/unconfirmed. And another 28 with one of [ segfault segmentation sigabrt sigsegv ] in a comment.

Re: [Libreoffice-qa] organizing our "crasher" bugs ?

2015-05-27 Thread Bjoern Michaelsen
Hi, On Wed, May 27, 2015 at 04:36:01PM +0200, Bjoern Michaelsen wrote: > Hi, > > On Wed, May 27, 2015 at 03:25:24PM +0100, Caolán McNamara wrote: > > What would work ideally for me is to someone get the subset of all > > crashes that are ~100% reproducible under Linux and ordered by the > > numbe

Re: [Libreoffice-qa] organizing our "crasher" bugs ?

2015-05-27 Thread Bjoern Michaelsen
Hi, On Wed, May 27, 2015 at 03:25:24PM +0100, Caolán McNamara wrote: > What would work ideally for me is to someone get the subset of all > crashes that are ~100% reproducible under Linux and ordered by the > number of steps required to reproduce. Any ideas on how to generate that > subset ? That

[Libreoffice-qa] organizing our "crasher" bugs ?

2015-05-27 Thread Caolán McNamara
There are ~190 bugs with the word "crash" in the summary in the states new/assigned/reopened/unconfirmed. As with the coverity, import-testing, export-testing stuff I think it would be helpful to start chewing into crashers in some systematic way where progress can be measured. 190 isn't a vast nu