Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index




On 03/06/2015 12:11 AM, Alex Thurgood wrote:
Le 06/03/2015 05:52, Joel Madero a écrit :

Hi Joel,

I'm curious if anyone has any thoughts about bugs that have backtraces
but QA has been unable to repro. Should these just be pushed to NEW ?

Currently there are 8 UNCONFIRMED crashers  - at least one or two of
those have backtraces but have had other members of QA say they cannot
reproduce.

Got a link for those issues handy ?
https://bugs.documentfoundation.org/buglist.cgi?list_id=525899&regetlastlist=525899

There are the 8 crashers currently reported and unconfirmed. At least 2
of them have backtraces - one of the other ones has some kind of a
system dump or something...

If we can just mark as NEW then I suggest we start automatically asking
users to do a backtrace (at least suggest and link to the wiki). Might
save a few rounds of NEEDINFO -> UNCONFIRMED -> NEEDINFO -> WFM ->
UNCONFIRMED ;)

Best,
Joel



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/


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.