Re: [Libreoffice-qa] organizing our crasher bugs ?
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 they are easy to reproduce and everything is there for devs to tackle them. I foresee a problem with recognizing Base crashers as important in the above scenario (I haven't checked to see whether there are any in the list). By their very nature, database crashers usually require more effort and more steps to reproduce than say, a formatting crasher bug in Writer or Calc, or a call to some function, due, among others, to the following : - Java : as ever, often problematic to debug from within gdb/lldb for the casual QAer - the internal JVM signal catcher often baulks without any really useful information when using debug builds ; - the variety of different db engines we support - we have two embedded engine possibilites, plus all the external possible backends and associated driver problems to factor in ; - the Report Builder - more Java, but funnily enough, most of the crashers in this seem to relate to changes in other areas of the code (Writer, Calc, OUString, configuration files). None of that could be considered easy. Alex ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] organizing our crasher bugs ?
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 systematic way where progress can be measured. 190 isn't a vast number in the over all scheme of things. 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 ? Bjoern already largely addressed this but bugzilla is hugely limited for organizing. What I think would be minimum (and can be done) is: Confirm each crash on 5.0; _Ensure_ that each has easy steps; _Ensure_ that each has been checked for regressions (and tagged accordingly in whiteboard/version field); _Ensure_ that each has a debug log; Prioritize correctly (Major/Critical High/Highest) For the most straight forward ones that have easy steps we can just mark them as critical + highest - signaling that they are easy to reproduce and everything is there for devs to tackle them. Best, Joel FYIW: I've been pushing this for about a year now ;) ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] organizing our crasher bugs ?
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 number of steps required to reproduce. Any ideas on how to generate that subset ? Another hint of a good, clean, solvable bug is a limited number of comments: https://bugs.documentfoundation.org/buglist.cgi?bug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDcolumnlist=product%2Ccomponent%2Cassigned_to%2Cshort_desc%2Cchangeddate%2Cop_sys%2Clongdescs.countlist_id=539737product=LibreOfficequery_format=advancedresolution=---short_desc=crashshort_desc_type=allwordssubstr once you have more than 10 comments on a bug, there is a high chance of some can reproduce on $foo, cant reproduce on $bar ping-pong going on. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] organizing our crasher bugs ?
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. https://bugs.documentfoundation.org/buglist.cgi?bug_status=UNCONFIRMEDbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDchfield=[Bug%20creation]chfieldto=Nowf1=longdescf2=short_desco1=anywordssubstro2=notsubstringorder=Bug%20Numberproduct=LibreOfficequery_format=advancedv1=segfault%20segmentation%20sigabrt%20sigsegvv2=crash And then are raised assertions, which crash only for people using paranoid build options. I think it would be good to leave them for another day. Just my C$0.02 worth. Terry. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
