Re: [Libreoffice-qa] minutes of ESC call ...
On 09/06/2012 06:55 PM, Michael Stahl wrote: On 06/09/12 17:42, Michael Meeks wrote: i don't have an opinion whether --enable-dbgutil should by default enable symbols or not. First of all, note that --enable-symbols is a misnomer. It is not per-se about any kind of symbols (like not stripping internal symbols on ELF, etc.), but rather about debugging information. (With GCC it enables -g Produce debugging information [http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/Debugging-Options.html#Debugging-Options] (or -g2, -ggdb2), with MSVC it enables /Zi enable debugging information [cl /? output].) My main concern for assert-enabled (i.e., --enable-dbgutil) builds is that if they abort, it is easy to get a decent backtrace. For that, it is important that internal symbols are not stripped, but much less so that --enable-symbols--controlled debugging information is available. Therefore, I have no decided opinion either on whether --enable-dbgutil should imply --enable-symbols by default. Stephan ___ 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] Regression test (Moztrap) test case localization temporary solution.
Hi Petr, all, On Thu, Sep 06, 2012 at 12:26:48PM +0200, Petr Mladek wrote: Yi Fan Jiang píše v Čt 06. 09. 2012 v 03:47 -0600: Yi Fan Jiang píše v Čt 06. 09. 2012 v 02:50 -0600: 4. In the page, make sure the version of the case is switched to *0* by: - Around the top right corner of the page, hover the mouse on the version selection list box right below the Select environment - Click the version initiated with 0, in this case, it should be 0 creating a table in database and increment records Would be possible to set 0 as the default version for editing? I am afraid that the current default setting is too error prone. It should be possible, I'll make a quick fix this week. Great. I keep my fingers crossed. Done, the page now only show version 0 cases: http://vm12.documentfoundation.org/manage/cases/ The following is some explanations: I did some investigation today and found each case/version pair stores as a single data record in database, so navigating between versions depend on the URL containing a specific case/version id. For example, the following refers to the same case with different version: http://vm12.documentfoundation.org/manage/caseversion/298/ http://vm12.documentfoundation.org/manage/caseversion/330/ By default the case management page filtering out only the *latest* version of a case and gives a specific editing url for each. I have thought to make a *seemless* transition to show the *latest* version but given a *0* version edit link, but felt it might bring some confusing. So I changed the filter to always show Version 0 instead of the *latest* version as a solution. Meanwhile switching among versions is still available by 2 ways: 1. click the Advance Filtering button and click Libreoffice x.x in product version criteria field. 2. click the pencil icon to edit a single case and switch the version inside. It is noticeable for those cases particularly created for a version X.Y while not existed in Version 0, only the way 1 is available. But I doubt it will be a usual case :) How do you think about that? Is this solution accepatble? Best wishes, Yifan -- Yifan Jiang Libreoffice / SuSE Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ 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] Regression test (Moztrap) test case localization temporary solution.
Yi Fan Jiang píše v Pá 07. 09. 2012 v 02:44 -0600: Hi Petr, all, On Thu, Sep 06, 2012 at 12:26:48PM +0200, Petr Mladek wrote: Yi Fan Jiang píše v Čt 06. 09. 2012 v 03:47 -0600: Yi Fan Jiang píše v Čt 06. 09. 2012 v 02:50 -0600: 4. In the page, make sure the version of the case is switched to *0* by: - Around the top right corner of the page, hover the mouse on the version selection list box right below the Select environment - Click the version initiated with 0, in this case, it should be 0 creating a table in database and increment records Would be possible to set 0 as the default version for editing? I am afraid that the current default setting is too error prone. It should be possible, I'll make a quick fix this week. Great. I keep my fingers crossed. Done, the page now only show version 0 cases: http://vm12.documentfoundation.org/manage/cases/ Cool. The following is some explanations: By default the case management page filtering out only the *latest* version. So I changed the filter to always show Version 0 instead of the *latest* version as a solution. Yup. this makes sense. Meanwhile switching among versions is still available by 2 ways: 1. click the Advance Filtering button and click Libreoffice x.x in product version criteria field. Ah, the advanced filtering is powerful and nice. Though, I am afraid that it is a bit confusing. You select the version in advanced filtering in one dialog (list of test cases) and by drop-down box in the other (edit test case). A solution would be to remove the version selection from the advanced filtering and add the version selection drop-down list instead. IMHO, this might be more clear and more intuitive. Well, we might try the current state and improve it if needed. It is noticeable for those cases particularly created for a version X.Y while not existed in Version 0, only the way 1 is available. But I doubt it will be a usual case :) If we show 0 by default, all test cases should be primary developed in this version. It is similar with the source development where everything is done primary in master branch. A test case for the version 0 is like a test case for master. We could create(branch) the test cases fot 3.7 release when we branch sources for 3.7. Another possibility would be to ignore the version 0 and branch 3.7 from 3.6 test cases. The question is when to do it. Also this might cause confusion because it is different from the source development model. In each case, people need to be careful what version of test cases they edit. BTW: Is it possible to easily copy test case from one version to the other using the UI? Or is there some alternative of git cherry-pick where you could apply changes to other branches? Anyway, I think that it looks reasonable now. Though, we need to hear feedback from the QA community. Non-developers might have different point of view. They are not that familiar git branches, ... Best Regards, Petr ___ 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] Regression test (Moztrap) test case localization temporary solution.
Hi Petr, On Fri, Sep 07, 2012 at 12:16:30PM +0200, Petr Mladek wrote: BTW: Is it possible to easily copy test case from one version to the other using the UI? Or is there some alternative of git cherry-pick where you could apply changes to other branches? Yes, the in-test-case version selection will list all existed versions, if the current case does not belong to a version, click the version number will create a new case version instance AND switching to it :) Anyway, I think that it looks reasonable now. Though, we need to hear feedback from the QA community. Non-developers might have different point of view. They are not that familiar git branches, ... Great to hear :) Thanks for the feedback! Best Regards, Petr -- Yifan Jiang Libreoffice / SuSE Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ 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/
[Libreoffice-qa] Please Triage These (Bugs from 2011)
There are 12 bugs from 2011 that haven't been triaged. I think they have been kind of ignored because they require certain things (such as Mac or UX input or advanced computer understanding :) ). Could someone(s) please get these done, then at least we're up to 2012 :) If you see one or more that you think you can deal with, please do it and send a reply so we know it's done. Thanks everyone ID▲https://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=bug_id%20DESCquery_based_on= Comphttps://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=component%2Cbug_severity%2Cpriority%2Cbug_idquery_based_on= Sev▲https://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=bug_severity%20DESC%2Cpriority%2Cbug_idquery_based_on= Pri▲https://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=priority%20DESC%2Cbug_severity%2Cbug_idquery_based_on= OShttps://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=op_sys%2Cbug_severity%2Cpriority%2Cbug_idquery_based_on= Assigneehttps://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=assigned_to%2Cbug_severity%2Cpriority%2Cbug_idquery_based_on= Statushttps://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=bug_status%2Cbug_severity%2Cpriority%2Cbug_idquery_based_on= Resolutionhttps://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=resolution%2Cbug_severity%2Cpriority%2Cbug_idquery_based_on= Summaryhttps://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=short_desc%2Cbug_severity%2Cpriority%2Cbug_idquery_based_on= Changedhttps://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=changeddate%2Cbug_severity%2Cpriority%2Cbug_idquery_based_on= 42673 https://bugs.freedesktop.org/show_bug.cgi?id=42673SpreadshmajlowWind libreoffice-b...@lists.free...unco---With disconnected network printers, Calc hangs opening some files waiting on the Windows print spoolerhttps://bugs.freedesktop.org/show_bug.cgi?id=42673 2011-11-0741987 https://bugs.freedesktop.org/show_bug.cgi?id=41987Libreoff normediummaclibreoffice-b...@lists.free...unco---LibreOffice hangs when Save As... tries to re-mount previously used, but now inaccessible network volumes https://bugs.freedesktop.org/show_bug.cgi?id=41987 2011-10-1942118 https://bugs.freedesktop.org/show_bug.cgi?id=42118BASICnor mediumlinulibreoffice-b...@lists.free...unco---Macro editor lacks the standard window controls -- Linux Unity window manager specifichttps://bugs.freedesktop.org/show_bug.cgi?id=42118 2011-11-1743185 https://bugs.freedesktop.org/show_bug.cgi?id=43185Libreoff normediumwindlibreoffice-b...@lists.free...unco---Font Replacement According Replacement Table (Option) does not Work as Expectedhttps://bugs.freedesktop.org/show_bug.cgi?id=43185 2011-11-2343198 https://bugs.freedesktop.org/show_bug.cgi?id=43198Libreoff normediumlinulibreoffice-b...@lists.free...unco---LibreOffice is opened when WebKitGtk is used with installed LibreOffice Mozilla pluginhttps://bugs.freedesktop.org/show_bug.cgi?id=43198 2011-11-2343255 https://bugs.freedesktop.org/show_bug.cgi?id=43255Drawing normediumwindlibreoffice-b...@lists.free...unco---FILEOPEN: MinGW impossible for particular .SVGshttps://bugs.freedesktop.org/show_bug.cgi?id=43255 2011-11-2643449 https://bugs.freedesktop.org/show_bug.cgi?id=43449Document normediumalllibreoffice-b...@lists.free...unco---WIKIHELP image size should be in pixel, or else trash resizinghttps://bugs.freedesktop.org/show_bug.cgi?id=43449 2011-12-0143450 https://bugs.freedesktop.org/show_bug.cgi?id=43450Document normediumalllibreoffice-b...@lists.free...unco---WIKIHELP table-styled list consistency https://bugs.freedesktop.org/show_bug.cgi?id=434502011-12-01 43471 https://bugs.freedesktop.org/show_bug.cgi?id=43471Libreoffminmedium linulibreoffice-b...@lists.free...unco---unable to import gtk library from libreoffice's embedded python on RHEL6.1https://bugs.freedesktop.org/show_bug.cgi?id=43471 2011-12-0242075 https://bugs.freedesktop.org/show_bug.cgi?id=42075UIenh mediumwindlibreoffice-b...@lists.free...unco---Add a scan-button to the select scanner-dialog https://bugs.freedesktop.org/show_bug.cgi?id=42075 2011-10-2043174 https://bugs.freedesktop.org/show_bug.cgi?id=43174Chartenh
Re: [Libreoffice-qa] Triage Project Update
Hi Nino, That's the beauty of our project, everyone's opinion is respected :) I'll try to avoid adding any work to website team and see what method works best to get these triaged and organized best. As of now, google doc + fdo seems to be doing the trick :) Ultimately might just make a macro to auto sort them once every other week to keep the google doc updated until the project is done (ie. getting all bugs 30 days old triaged so we can try to stick with a goal of triaging withing 30 days for new bugs). Thanks for all the valuable input. Best Regards, Joel On Tue, Sep 4, 2012 at 3:07 PM, Nino Novak nn.l...@kflog.org wrote: Am 04.09.2012 23:05 schrieb Joel Madero: I agree that FDO has some benefits but the limitation is really that each user is needed to query every time, the possibility of overlap is great, and no one is really responsible for an individual bug until the query is made and someone takes the time to look into it. I'm not sure if others would agree but it seems like having a group of 50 or so and being able to just do those at your convenience makes people more likely to help and feel like their is an end in sight for their portion. This is vs. just seeing a never ending list from FDO or even having to teach new users (or even not new users) exactly what to search for every time with FDO. As for me (a rather unexperienced QA Newbie), I've chosen a somewhat different approach: I've first created two custom searches, 1) all recent bugs (reported within the last two days) for curiosity (just to see what people report recently) 2) all UNCONFIRMED bugs from the last 14 days From query 2 I picked a couple of bugs every couple of days to reproduce/confirm/assign/close/whatever seemed appropriate. That's just to show a slightly different approach, which is rather simple and can be handled perfectly within bugzilla itself without any external tool. Ok, the only problem was, that when a person starts reproducing a bug, it can happen, that another triager just starts with the very same bug at the same time. So some kind of lock signal was the only missing thing to prevent duplication of work. However, this situation did not happen a single time during my self-chosen BugReviewWeek ;-) Another advantage: By the above process nobody (virtually) blocks 50 bugs for a longer time period. Bugzilla queries are very adequate at every time, as all works with live data. Similar to how developers assign themselves bugs and then can just go look at their own bugs (My Bugs) it would be nice to have this ability for QA triagers but have it somewhat automated since it's just triaging, not programming. In the long run (once we're through the back log of 650+ that are really old), it would be amazing if we had a team of QA staff that signed up to have bugs auto assigned to them for triaging. We have the libreoffice-bugs@fdo mailing list, which contains (nearly?) every new bug. Could we use it somehow for this purpose? E.g. by replying to a bug or forwarding it to the qa list or some such? (Just thoughts, nothing concrete) What I imagine: QA triagers sign up for components they are willing to triage and their max load New bug is reported, if the bug has a component listed the bug gets auto assigned for triaging purposes according to some rule(s) Personally, I prefer not to sign up for a special component but to pick a recent bug which kind of attracts me spontanously. But there might be other opinions/preferences/arguments/approaches. For now the google docs works, FDO does not as it is now but I'll discuss this further with Bjoern, Petr Rainer to see if we can come up with something more functional than the chaos that is FDO :) Or maybe I'm just not familiar enough with FDO to really feel comfortable myself with it, this is more likely than not true :) :-) I like your initiative. Please don't feel discouraged by my comments, I just wanted to add a slightly different view. If people like your approach, that's great! It does not contradict to mine (IMHO), as it's rather obvious if a bug has been triaged or not. So we can all work together towards our common goal. Regards, Nino ___ 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/
[Libreoffice-qa] How Can I Provide More Info For Developers
Hi All, Came across this bug FDO#45570 and I've already nominated as a most annoying bug but I think that devs might appreciate me getting some kind of a log or something together for the crash. What type of log should I create and how do I go about doing this (basic steps, my knowledge of terminology is still in the first stages :) ). Thanks everyone Best Regards, Joel ___ 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] How Can I Provide More Info For Developers
On Fri, Sep 7, 2012 at 6:11 PM, Joel Madero jmadero@gmail.com wrote: Hi All, Came across this bug FDO#45570 and I've already nominated as a most annoying bug but I think that devs might appreciate me getting some kind of a log or something together for the crash. What type of log should I create and how do I go about doing this (basic steps, my knowledge of terminology is still in the first stages :) ). Thanks everyone Best Regards, Joel Just some random thoughts here: What happens when you create a 'working document', thats been opened and saved in Msoffice or OpenOffice, and then try to open that saved doc in LibreOffice ? Does the issue still appear ? Also, would it be helpful to attach such a document to the bug report for troubleshooting purposes ? - John Smith. ___ 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] How Can I Provide More Info For Developers
I don't see that helping much, as the developer who takes this one can quickly do this themselves. A working doc only takes 2 seconds to make. Best Regards, Joel On Fri, Sep 7, 2012 at 9:35 AM, John Smith lbalba...@gmail.com wrote: On Fri, Sep 7, 2012 at 6:11 PM, Joel Madero jmadero@gmail.com wrote: Hi All, Came across this bug FDO#45570 and I've already nominated as a most annoying bug but I think that devs might appreciate me getting some kind of a log or something together for the crash. What type of log should I create and how do I go about doing this (basic steps, my knowledge of terminology is still in the first stages :) ). Thanks everyone Best Regards, Joel Just some random thoughts here: What happens when you create a 'working document', thats been opened and saved in Msoffice or OpenOffice, and then try to open that saved doc in LibreOffice ? Does the issue still appear ? Also, would it be helpful to attach such a document to the bug report for troubleshooting purposes ? - John Smith. ___ 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] How Can I Provide More Info For Developers
On Fri, Sep 7, 2012 at 6:38 PM, Joel Madero jmadero@gmail.com wrote: I don't see that helping much, as the developer who takes this one can quickly do this themselves. A working doc only takes 2 seconds to make. Best Regards, Joel Another random thought then: Is there a way to reproduce the issue that doesnt require the installation of Lotus Domino ? - John Smith. ___ 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] How Can I Provide More Info For Developers
Wrong Bug, dammit, my bad. Here is the proper one, attachment is there and functioning, I had 5 open FDO tabs in FF and picked the wrong one. https://bugs.freedesktop.org/show_bug.cgi?id=48569 My apologies Joel On Fri, Sep 7, 2012 at 9:57 AM, John Smith lbalba...@gmail.com wrote: On Fri, Sep 7, 2012 at 6:38 PM, Joel Madero jmadero@gmail.com wrote: I don't see that helping much, as the developer who takes this one can quickly do this themselves. A working doc only takes 2 seconds to make. Best Regards, Joel Another random thought then: Is there a way to reproduce the issue that doesnt require the installation of Lotus Domino ? - John Smith. ___ 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] How Can I Provide More Info For Developers
On Fri, Sep 7, 2012 at 6:59 PM, Joel Madero jmadero@gmail.com wrote: Wrong Bug, dammit, my bad. Here is the proper one, attachment is there and functioning, I had 5 open FDO tabs in FF and picked the wrong one. https://bugs.freedesktop.org/show_bug.cgi?id=48569 My apologies Joel Maybe im just dumb, but: Once you have provided a reliable and reproducible test case (in this case, download the odt file attached to the report and save it as docx in libreoffice), is there still a need to provide further info at all ? The person tackling the bug can get all the info required on his/her own system, then ? Just my 2$. - John Smith. ___ 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] How Can I Provide More Info For Developers
Hi John, On Fri, 2012-09-07 at 19:10 +0200, John Smith wrote: Maybe im just dumb, but: Once you have provided a reliable and reproducible test case (in this case, download the odt file attached to the report and save it as docx in libreoffice), is there still a need to provide further info at all ? You can always make it easier for a developer to solve - and the easier it is, the more likely it is to get solved quickly. Ways to do that are: * getting a stack-trace with full debugging symbols * running valgrind with full debugging symbols and attaching a trace. For bonus points poking around at the code that's failing and thinking hard about it - and (for some bugs) even a non-expert can see the silliness by reading the relevant code in the backtrace, and looking at the git history for that file ;-) So anything to get more people drawn into development and bug fixing is good :-) we have no-where near enough hackers / proctologists to match the bugs (yet). ATB, Michael. -- michael.me...@suse.com , Pseudo Engineer, itinerant idiot ___ 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] How Can I Provide More Info For Developers
On Fri, Sep 7, 2012 at 7:24 PM, Michael Meeks michael.me...@suse.com wrote: Hi John, You can always make it easier for a developer to solve - and the easier it is, the more likely it is to get solved quickly. Ways to do that are: * getting a stack-trace with full debugging symbols * running valgrind with full debugging symbols and attaching a trace. If this is the case, maybe pre-build binaries with full debugging symbols should be made available for download (more) easily: both for releases and daily master builds ? Also, a 'howto' on how to do this (on linux, with gdb, on windows, with windbg ?) would be nice to have ? - John Smith. ___ 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] How Can I Provide More Info For Developers
On Fri, Sep 7, 2012 at 10:44 AM, John Smith lbalba...@gmail.com wrote: On Fri, Sep 7, 2012 at 7:24 PM, Michael Meeks michael.me...@suse.com wrote: Hi John, You can always make it easier for a developer to solve - and the easier it is, the more likely it is to get solved quickly. Ways to do that are: * getting a stack-trace with full debugging symbols * running valgrind with full debugging symbols and attaching a trace. Sounds good, but I agree with John that better instructions are needed. I'm working on a new triage page and hopefully in there we can get someone to contribute incredibly precise, easy for noobs, instructions for every type of backtrace/debug. Right now they are really written by experts for experts (IMO). I would backtrace much more frequently if I could follow the instructions on how to do it. Every time I feel like I have to go on IRC and ask 100 questions. If this is the case, maybe pre-build binaries with full debugging symbols should be made available for download (more) easily: both for releases and daily master builds ? Also, a 'howto' on how to do this (on linux, with gdb, on windows, with windbg ?) would be nice to have ? I don't think we have enough people packaging to make pre-built binaries for everyone. Plus, these are huge, my install is 22 gigs with all symbols on, not very good for packaging purposes. Best Regards, Joel - John Smith. ___ 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] How Can I Provide More Info For Developers
The best solution would be to have a debug symbol server, then there would be easily accessible debug symbols even for the release builds. ___ 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] How Can I Provide More Info For Developers
On Fri, Sep 7, 2012 at 9:42 PM, Joel Madero jmadero@gmail.com wrote: Sounds good, but I agree with John that better instructions are needed. I'm working on a new triage page and hopefully in there we can get someone to contribute incredibly precise, easy for noobs, instructions for every type of backtrace/debug. Right now they are really written by experts for experts (IMO). I would backtrace much more frequently if I could follow the instructions on how to do it. Every time I feel like I have to go on IRC and ask 100 questions. I don't think we have enough people packaging to make pre-built binaries for everyone. Plus, these are huge, my install is 22 gigs with all symbols on, not very good for packaging purposes. I guess it all depends on who your target audience is. If you really want end-users (libre office users) to provide backtraces, you really need to make the threshold for doing that as low as possible. I dont think it is reasonable to have end-users compile source code for themselves; especially on windows, where it requires msvc or cygwin to do so. ___ 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] How Can I Provide More Info For Developers
On Fri, Sep 7, 2012 at 9:49 PM, Joel Madero jmadero@gmail.com wrote: I'll bring this up at our next conference call and see if there is a possible solution. Best Regards, Joel May I humbly note that I personally feel that developers should be able to produce their own backtraces, given a solid reproducible test-case in the bug report ? Perhaps effort would be better spend on: 1.) teaching end-users how to provide a reproducible test case in a bug report 2.) teaching devs on how to produce backtraces instead of: 1.) teaching end-users how to install symbol binaries and backtrace them on their platform ? Just my 2$ - John Smith. ___ 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] How Can I Provide More Info For Developers
This isn't for end-users, it's for QA team..and it's our job to do as much as possible to help the developers. I know when I'm doing the development side I appreciate whatever previous info users and QA can provide. It's maximizing the efficiency of our abilitieslimited # of developers means we should be using their time wisely, not running backtraces that someone with 1/10th of their computer programming skills could manage just fine. Best Regards, Joel On Fri, Sep 7, 2012 at 12:56 PM, John Smith lbalba...@gmail.com wrote: On Fri, Sep 7, 2012 at 9:49 PM, Joel Madero jmadero@gmail.com wrote: I'll bring this up at our next conference call and see if there is a possible solution. Best Regards, Joel May I humbly note that I personally feel that developers should be able to produce their own backtraces, given a solid reproducible test-case in the bug report ? Perhaps effort would be better spend on: 1.) teaching end-users how to provide a reproducible test case in a bug report 2.) teaching devs on how to produce backtraces instead of: 1.) teaching end-users how to install symbol binaries and backtrace them on their platform ? Just my 2$ - John Smith. ___ 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] How Can I Provide More Info For Developers
On Fri, Sep 7, 2012 at 9:59 PM, Joel Madero jmadero@gmail.com wrote: This isn't for end-users, it's for QA team..and it's our job to do as much as possible to help the developers. I know when I'm doing the development side I appreciate whatever previous info users and QA can provide. It's maximizing the efficiency of our abilitieslimited # of developers means we should be using their time wisely, not running backtraces that someone with 1/10th of their computer programming skills could manage just fine. Best Regards, Joel Well, like I said: I guess it all depends on who your target audience is. Just keep in mind who that is, and what their expected skill set is, and adjust your procedures to that. IMHO. - John Smith. ___ 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/
