ABRT server to start publishing to Fedmsg
Hi everyone,
We're excited to announce that the ABRT server [1] will start publishing to
Fedmsg. Currently there are two general topics available:
* faf.report.threshold{1,10,100,1000,1,10,100} is fired whenever a
crash report occurrence reaches the given threshold.
* faf.problem.threshold{1,10,100,1000,1,10,100} is the same, but
for problems (similar crash reports clustered together)
Both contain names of the affected package, so you can easily configure email
notifications about packages you maintain on the FMN [2], e.g. you could be
notified whenever a crash occurs in your package 1 000 times and start
investigating the problem. By default, packagers will receive all notifications
with a threshold of 10 and higher for their packages, but you may want to prune
those down to only problems with more frequent occurrence.
Please feel free to contact us [3,4] with any questions, suggestions, issues or
feature request.
For the ABRT and Fedmsg teams,
Marek
[1] https://retrace.fedoraproject.org/faf/
[2] https://apps.fedoraproject.org/notifications/
[3] https://github.com/abrt/faf or #abrt on freenode
[4] http://www.fedmsg.com/en/latest/#community
___
devel-announce mailing list
devel-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
ABRT server to start publishing to Fedmsg
Hi everyone,
We're excited to announce that the ABRT server [1] will start publishing to
Fedmsg. Currently there are two general topics available:
* faf.report.threshold{1,10,100,1000,1,10,100} is fired whenever a
crash report occurrence reaches the given threshold.
* faf.problem.threshold{1,10,100,1000,1,10,100} is the same, but
for problems (similar crash reports clustered together)
Both contain names of the affected package, so you can easily configure email
notifications about packages you maintain on the FMN [2], e.g. you could be
notified whenever a crash occurs in your package 1 000 times and start
investigating the problem. By default, packagers will receive all notifications
with a threshold of 10 and higher for their packages, but you may want to prune
those down to only problems with more frequent occurrence.
Please feel free to contact us [3,4] with any questions, suggestions, issues or
feature request.
For the ABRT and Fedmsg teams,
Marek
[1] https://retrace.fedoraproject.org/faf/
[2] https://apps.fedoraproject.org/notifications/
[3] https://github.com/abrt/faf or #abrt on freenode
[4] http://www.fedmsg.com/en/latest/#community
___
devel-announce mailing list
devel-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
abrt server report: 20140526
In last two weeks these components were crashing the most: 1. kernel seen 56703 times (31% of all reports) http://retrace.fedoraproject.org/faf/problems/1597313/ RHBZ#1030988 http://retrace.fedoraproject.org/faf/problems/749325/ 2. virtuoso-opensource seen 19395 times (11% of all reports) http://retrace.fedoraproject.org/faf/problems/1279374/ RHBZ#1013705 http://retrace.fedoraproject.org/faf/problems/740642/ RHBZ#1013705 3. tracker seen 9474 times (5% of all reports) http://retrace.fedoraproject.org/faf/problems/1697689/ RHBZ#967021 http://retrace.fedoraproject.org/faf/problems/1734513/ RHBZ#997752 4. kde-workspace seen 9326 times (5% of all reports) http://retrace.fedoraproject.org/faf/problems/1611104/ http://retrace.fedoraproject.org/faf/problems/1259854/ 5. firefox seen 8891 times (5% of all reports) http://retrace.fedoraproject.org/faf/problems/1700469/ http://retrace.fedoraproject.org/faf/problems/1538076/ Hot problems: ID Components Count --- 1279374virtuoso-opensource11840 749325 kernel 10119 1611104kde-workspace 9266 1597313kernel 8609 740642 virtuoso-opensource 6696 1739523kernel 4497 1160331evolution-data-server 3335 1370858kernel 2575 1700469firefox 2498 1266680gvfs1968 URL: http://retrace.fedoraproject.org/faf/problems/hot/ Long-term problems: ID Components Count --- 1127716glib-networking403503 908821 kernel 155545 577402 libgsf 108086 1174076kernel 106820 727281 xulrunner 86996 57483 blueman85632 1199622xulrunner 75125 1340164glib-networking67872 740642 virtuoso-opensource62350 1739523kernel 60040 URL: http://retrace.fedoraproject.org/faf/problems/longterm/ Most destabilized components: Component Jump Graph -- kde-workspace -4 ▁▁▁▃█▆▁ kernel 2151 ▁▁▁▆▃▅█ firefox 324 ▄▁▂▁█▃▇ getmail 381 ▂▃█ virtuoso-opensource 260 ▂▁▂▇█▁▃ Most stabilized components: Component Jump Graph -- tracker -183 ▃▇█▃▅▁▁ xulrunner -198 ▅▇█▂▂▁▁ gnome-shell -193 ▄█▆▅▄▂▁ nautilus -86 ▅█▆▅▅▁▁ blueman -70 ▆▅█▇▇▂▁ Server URL: http://retrace.fedoraproject.org/faf/ Report a bug: https://github.com/abrt/faf/issues/new Server sources: https://github.com/abrt/faf -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
abrt server report: 20130917
In last two weeks these components were crashing the most: 1. kernel seen 85925 times (52% of all reports) https://retrace.fedoraproject.org/faf/problems/1174076/ https://retrace.fedoraproject.org/faf/problems/1209703/ 2. xulrunner seen 10191 times (6% of all reports) https://retrace.fedoraproject.org/faf/problems/727281/ https://retrace.fedoraproject.org/faf/problems/757169/ 3. glib-networking seen 8701 times (5% of all reports) https://retrace.fedoraproject.org/faf/problems/1127716/ RHBZ#998232 https://retrace.fedoraproject.org/faf/problems/1154608/ 4. tracker seen 5771 times (4% of all reports) https://retrace.fedoraproject.org/faf/problems/869238/ RHBZ#966764 https://retrace.fedoraproject.org/faf/problems/1250621/ RHBZ#957533 5. gnome-shell seen 4673 times (3% of all reports) https://retrace.fedoraproject.org/faf/problems/864616/ RHBZ#953325, RHBZ#1002524 https://retrace.fedoraproject.org/faf/problems/20295/ RHBZ#827158, RHBZ#905168 Hot problems: ID Components Count --- 1174076kernel 26633 1127716glib-networking 8243 1209703kernel 6318 727281 xulrunner 4872 138934 meld3927 57483 blueman 2798 1059468kernel 2748 1178557kernel 2369 1173865kernel 1686 1146230kernel 1580 URL: https://retrace.fedoraproject.org/faf/problems/hot/ Long-term problems: ID Components Count --- 577402 libgsf 77299 1174076kernel 70639 727281 xulrunner 54614 57483 blueman35539 757169 xulrunner 31407 20295 gnome-shell29302 898437 kernel 24020 244577 xulrunner 21868 365559 setroubleshoot 18585 138934 meld 17977 URL: https://retrace.fedoraproject.org/faf/problems/longterm/ Most destabilized components: Component Jump Graph -- kernel 2398 ▁▄▄▅▃█▇ glib-networking 2004 ▁▁▂█▄▄▆ tracker 464 ▁▁▂▄▂█▅ xulrunner465 ▁▁█▄▄▅▄ PackageKit 240 ▁▁▃▇▇█▇ Most stabilized components: Component Jump Graph -- meld 67 ▄█▆▅▁▁▆ pulseaudio -26 ▄█▁▁▂▂▃ policycoreutils -4 ▁█▁ libgsf23 ▂█▄▄▁▂▄ yum -6 ▃█▃▃▃▁▁ Server URL: https://retrace.fedoraproject.org/faf/ Report a bug: https://github.com/abrt/faf/issues/new Server sources: https://github.com/abrt/faf -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: abrt server report: 20130917
On Tue, Sep 17, 2013 at 03:57:55PM +0200, Michal Toman wrote: In last two weeks these components were crashing the most: 1. kernel seen 85925 times (52% of all reports) https://retrace.fedoraproject.org/faf/problems/1174076/ https://retrace.fedoraproject.org/faf/problems/1209703/ I've noticed a problem in your code that attributes blame to the 'function' field. In that second trace: Call Trace: [c043e33b] ? print_hardware_dmi_name+0x2b/0x30 [c043e3a3] warn_slowpath_common+0x63/0x80 [f7ea8413] ? carl9170_op_tx+0x733/0x810 [carl9170] [f7ea8413] ? carl9170_op_tx+0x733/0x810 [carl9170] [c043e462] warn_slowpath_null+0x22/0x30 [f7ea8413] carl9170_op_tx+0x733/0x810 [carl9170] the '?' fields are junk on the stack, and not actually the functions we're in. Instead of blaming print_hardware_dmi_name, this trace should be attributed to carl9170_op_tx. Everything else above that is either noise on the stack from previous calls, or parts of the dump trace logic. I'd ignore the ? functions completely for this purpose. Dave -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
abrt server report: 20130830
In last two weeks these components were crashing the most: 1. kernel seen 88743 times (58% of all reports) http://retrace.fedoraproject.org/faf/problems/1174076/ http://retrace.fedoraproject.org/faf/problems/909608/ 2. xulrunner seen 7513 times (5% of all reports) http://retrace.fedoraproject.org/faf/problems/727281/ http://retrace.fedoraproject.org/faf/problems/757169/ 3. tracker seen 5447 times (4% of all reports) http://retrace.fedoraproject.org/faf/problems/468273/ http://retrace.fedoraproject.org/faf/problems/1186527/ 4. meld seen 3947 times (3% of all reports) http://retrace.fedoraproject.org/faf/problems/138934/ RHBZ#971948 http://retrace.fedoraproject.org/faf/problems/997382/ 5. blueman seen 3781 times (2% of all reports) http://retrace.fedoraproject.org/faf/problems/57483/ RHBZ#878795 http://retrace.fedoraproject.org/faf/problems/20903/ RHBZ#875682 Hot problems: ID Components Count --- 1174076kernel 28063 909608 kernel 7179 138934 meld3896 727281 xulrunner 3233 57483 blueman 2737 1059468kernel 2379 1178557kernel 2333 822352 kernel 2163 1146230kernel 1364 757169 xulrunner 1213 URL: http://retrace.fedoraproject.org/faf/problems/hot/ Long-term problems: ID Components Count --- 577402 libgsf 76735 727281 xulrunner 48737 57483 blueman32102 757169 xulrunner 30005 20295 gnome-shell28922 898437 kernel 24020 244577 xulrunner 21813 365559 setroubleshoot 18580 975227 evolution-data-server 17280 157490 mate-notification-daemon 16828 URL: http://retrace.fedoraproject.org/faf/problems/longterm/ Most destabilized components: Component Jump Graph -- kernel 3367 ▃▁▁▁▅▇█ mate-notification-daemon 531 ▁▁█ xulrunner222 ▁▃▄▂█▃▃ meld 41 ▆▁▁▇▅▇█ xscreensaver 13 ▂▁▃▆█▅▃ Most stabilized components: Component Jump Graph -- authconfig 1 ▁█▁ tracker -82 ▅▁▄█▁▂▁ virtuoso-opensource -3 ▁█▁ kdeartwork -29 █▃▁▃▃▂▁ totem-21 ▅▂█▁▂▃▁ Server URL: http://retrace.fedoraproject.org/faf/ Report a bug: https://github.com/abrt/faf/issues/new Server sources: https://github.com/abrt/faf Dry run enabled, not sending any emails -- Richard Marko -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
abrt server report: 20130129
Hot problems: ID Components Count --- 185766 kernel 1294 204154 kernel 1198 85820 yumex786 100106 gnome-packagekit 754 221206 kernel 741 258569 kernel 690 20295 gnome-shell 669 57483 blueman 579 83012 tracker 555 273202 rhythmbox543 URL: https://retrace.fedoraproject.org/faf/problems/hot/ Long-term problems: ID Components Count --- 275755 kernel 3301 58474 kernel 2408 100106 gnome-packagekit2012 83012 tracker 1825 20085 gnome-terminal 1362 19369 control-center 1317 117749 gnome-packagekit1078 274020 kernel 990 20171 gnome-shell 977 85820 yumex917 URL: https://retrace.fedoraproject.org/faf/problems/longterm/ Most destabilized components: Component Jump Graph -- kernel 783 ▁▅▃▂▆▃█ gvfs 34 ▁▁▁▃█▇▅ gnome-shell 76 ▂▂▁▂▁▁█ blueman8 ▄▁▃▄▅█▆ evolution 34 ▁▄▁▅▁▁█ Most stabilized components: Component Jump Graph -- gnome-settings-daemon-22 ▄█▆▄▁▁▁ dconf-29 █▅▆ gnome-terminal -22 █▆▃▁▁▁▂ libreoffice -16 █▆▅▂▃▁▄ setroubleshoot -16 ▆▆█▅▄▂▁ Server URL: https://retrace.fedoraproject.org/faf/ Report a bug: https://fedorahosted.org/abrt/newticket?component=faf Server sources: http://git.fedorahosted.org/cgit/faf.git/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
abrt server report: 20130117
Hot problems: ID Components Count --- 34452 dconf450 28310 kernel 379 228274 kernel 327 100106 gnome-packagekit 324 83012 tracker 225 20085 gnome-terminal 218 214662 gvfs 200 202102 kernel 191 85820 yumex181 208485 mate-file-manager168 URL: https://retrace.fedoraproject.org/faf/problems/hot/ Long-term problems: ID Components Count --- 28310 kernel 2635 228274 kernel 2083 100106 gnome-packagekit1359 83012 tracker 1344 19369 control-center 1306 20085 gnome-terminal 1230 117748 gnome-packagekit 995 202102 kernel 944 20171 gnome-shell 903 227973 glib2, gtk3 826 URL: https://retrace.fedoraproject.org/faf/problems/longterm/ Most destabilized components: Component Jump Graph -- kernel 1265 ▁▄█ tracker 210 ▁▁▁▂▂▄█ gnome-shell 179 ▂▃█ rhythmbox102 ▁▃█ yumex 91 ▁▃█ Most stabilized components: Component Jump Graph -- mate-file-manager 14 ▁▁█▃▁▁▁ ibus -12 ▃▃▁█▁▁▁ ibus-pinyin -7 █▆▄▆▃▁▁ tumbler -5 █▅▃▅▃▁▃ gwibber -6 █▂▃▁▃▁▁ Server URL: https://retrace.fedoraproject.org/faf/ Report a bug: https://fedorahosted.org/abrt/newticket?component=faf Server sources: http://git.fedorahosted.org/cgit/faf.git/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
abrt server report: 20130107
Hot problems: ID Components Count --- 186587 kernel 411 186872 kernel 350 185998 gnome-packagekit 212 187697 kernel 170 20085 gnome-terminal 162 20171 gnome-shell 127 83012 tracker 126 117748 gnome-packagekit 116 21780 control-center 110 165889 kernel 100 URL: https://retrace.fedoraproject.org/faf/problems/hot/ Long-term problems: ID Components Count --- 186587 kernel 2546 186872 kernel 1381 185998 gnome-packagekit1366 19369 control-center 1294 83012 tracker 1166 20085 gnome-terminal 1083 117748 gnome-packagekit 917 187697 kernel 871 20171 gnome-shell 825 54879 tracker 723 URL: https://retrace.fedoraproject.org/faf/problems/longterm/ Most destabilized components: Component Jump Graph -- kernel 116 ▁▁█▄▃▅▅ control-center49 ▁▁▂▄▃▄█ gnome-shell 38 ▂▁▃▄▃▆█ evolution 35 ▁▁▃▃▃▆█ evince27 ▁▁▂▁▁▂█ Most stabilized components: Component Jump Graph -- zenity -36 █▂▁ pulseaudio-2 ▃▆█▅▁▃▂ NetworkManager-4 ▆█▂▅▁▃▁ rhythmbox-13 █▁▆▁▆▇▁ simple-scan -3 ▆█▂▁▅▂▂ Server URL: https://retrace.fedoraproject.org/faf/ Report a bug: https://fedorahosted.org/abrt/newticket?component=faf Server sources: http://git.fedorahosted.org/cgit/faf.git/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
abrt server report: 20121211
Hot problems: ID Components Count --- 121163 kernel 344 118396 kernel 316 100107 gnome-packagekit 204 117748 gnome-packagekit 199 19369 control-center 154 20085 gnome-terminal 137 123131 kernel 131 83012 tracker 130 119523 kernel 122 112152 mate-session-manager 121 URL: https://retrace.fedoraproject.org/faf/problems/hot/ Long-term problems: ID Components Count --- 121163 kernel 1802 19369 control-center 1209 100107 gnome-packagekit1008 83012 tracker 944 118396 kernel 806 20085 gnome-terminal 802 117748 gnome-packagekit 687 121884 tracker 624 54879 tracker 616 109109 zenity 602 URL: https://retrace.fedoraproject.org/faf/problems/longterm/ Most destabilized components: Component Jump Graph -- mate-session-manager 17 ??? alacarte 9 ??? gcalctool 3 ??? firefox 11 ??? vino 7 ??? Most stabilized components: Component Jump Graph -- kernel -33 ??? tracker -16 ??? python-1 ??? gnome-packagekit -20 ??? mate-file-manager -9 ??? Server URL: https://retrace.fedoraproject.org/faf/ Report a bug: https://fedorahosted.org/abrt/newticket?component=faf Server sources: https://git.fedorahosted.org/cgit/faf.git/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
abrt server report: 20121126
Hot problems: ID Components Count --- 90599 kernel 406 91614 kernel 303 90633 gnome-packagekit 212 92490 zenity 170 83012 tracker 163 19369 control-center 154 83612 tracker 145 92352 kernel 137 21780 control-center 137 20085 gnome-terminal 135 URL: http://retrace.fedoraproject.org/faf/problems/hot/ Long-term problems: ID Components Count --- 90599 kernel 1449 19369 control-center 1047 90633 gnome-packagekit 834 83012 tracker 811 20085 gnome-terminal 657 45076 tracker 613 54879 tracker 545 21794 control-center 526 83612 tracker 520 92490 zenity 513 URL: http://retrace.fedoraproject.org/faf/problems/longterm/ Most destabilized components: Component Jump Graph -- kernel 5 ??? gnome-terminal14 ??? ailurus4 ??? gnome-packagekit 14 ??? alacarte 3 ??? Most stabilized components: Component Jump Graph -- tracker -20 ??? evolution-11 ??? rhythmbox-14 ??? control-center-5 ??? java-1.7.0-openjdk-5 ??? Server URL: http://retrace.fedoraproject.org/faf/ Report a bug: https://fedorahosted.org/abrt/newticket?component=faf Server sources: http://git.fedorahosted.org/cgit/faf.git/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: abrt server report: 20121004
On 10/04/2012 08:13 PM, Dave Jones wrote: On Thu, Oct 04, 2012 at 11:10:47AM -0400, Dave Jones wrote: Feature request: Can you do the same backtrace hashing abrt does, and provide a link to any bugs in bugzilla with the abrt_hash in the whiteboard ? Never mind. It seems you do that, and I was looking at reports where no bug had been filed. Perhaps print no bug filed yet in that case ? Something else just occurred to me, that might be useful, would be to print the top-most function in the summary page. Looking at https://retrace.fedoraproject.org/faf/problems/hot/*/*/kernel/ it would be useful if I could see at a glance that bug 13935 was a wireless bug, without needing to click into it. I agree. But... A lot of the 'function' fields on kernel bugs are going to be the same. warn_slowpath_common or warn_slowpath_null. We have a billion WARN() statements all over the kernel, and it's more useful knowing the location of where those are placed than the function name of the WARN statement. We will add the location and line numbers to these reports but the implementation is not ready yet. Ie, the summary for https://retrace.fedoraproject.org/faf/problems/13955/ should show function: brcms_c_wait_for_tx_completion. There may be a few other function names that would also require similar special casing. Sounds good. I've created tickets for all these improvements. Thanks! -- Richard Marko -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: abrt server report: 20121004
On 10/05/2012 04:48 AM, Adam Williamson wrote: On Thu, 2012-10-04 at 11:10 -0400, Dave Jones wrote: Feature request: Can you do the same backtrace hashing abrt does, and provide a link to any bugs in bugzilla with the abrt_hash in the whiteboard ? Never mind. It seems you do that, and I was looking at reports where no bug had been filed. Perhaps print no bug filed yet in that case ? Wait, how do we have reports with no bugs? If you cancel reporting to the bugzilla or it isn't successful no bug is assigned to the report on the server. It might be added later when someone completes the reporting. -- Richard Marko -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
abrt server report: 20121004
Hot problems: ID Components Count --- 11834 GConf2 199 11523 control-center 186 8300 kdebase-runtime, glibc, glib2, qt161 11431 kernel 159 11514 kernel 151 12245 control-center 134 11656 gnome-packagekit 129 6217 tracker 114 13018 tracker 107 6863 glibc, glib2 106 URL: https://retrace.fedoraproject.org/faf/problems/hot/ Long-term problems: ID Components Count --- 11523 control-center 375 11656 gnome-packagekit 358 12245 control-center 326 6863 glibc, glib2 302 7137 gnome-packagekit 292 8080 tracker 267 6217 tracker 266 6975 gnome-terminal 240 13018 tracker 220 9408 cairo, libX11, gtk3 217 URL: https://retrace.fedoraproject.org/faf/problems/longterm/ Most destabilized components: Component Jump Graph -- kernel 220 ▁▂▄▅▇▇█ nepomuk-core 35 ▁▂▆▃▆█▅ gnome-shell 11 ▄▃▁▁█▁▇ coreutils 2 █▂▁ xfce4-panel7 ▁▁▃▃▁▆█ Most stabilized components: Component Jump Graph -- tracker -23 ▆▆█▆▂▃▁ libreport 2 ▁█▅ totem-16 ▇█▁▃▃▁▂ java-1.7.0-openjdk-9 █▆▁▁▁▃▂ GConf2 -11 █▂▁▇▁▃▃ What's this about? -- These are the statistics generated by ABRT Server deployed on [1]. We are going to send these reports weekly as they should help developers prioritize their work. We expect them to become more and more accurate as more people will start using new versions of ABRT with simplified reporting [2]. Note that kernel is incorrectly blamed as the most destabilized component as we started handling kerneloops reports only last week. Feedback is really appreciated mainly on these topics: - structure of this email, - clustering quality, - backtrace quality, - kerneloops processing. [1] https://retrace.fedoraproject.org/faf/ [2] https://fedoraproject.org/wiki/Features/SimplifiedCrashReporting -- Richard Marko -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: abrt server report: 20121004
On Thu, Oct 4, 2012 at 3:52 PM, Richard Marko rma...@redhat.com wrote: Hot problems: ID Components Count --- 11834 GConf2 199 11523 control-center 186 Could we make the referenced ID the RHBZ ID for the crash. It makes it more useful for people to cross reference. I have no idea what that ID stands for and for example is 11843 a single problem with GConf2 that has occurred 199 times or is that all the problems for GConf2 added up. Peter These are the statistics generated by ABRT Server deployed on [1]. We are going to send these reports weekly as they should help developers prioritize their work. We expect them to become more and more accurate as more people will start using new versions of ABRT with simplified reporting [2]. Note that kernel is incorrectly blamed as the most destabilized component as we started handling kerneloops reports only last week. Feedback is really appreciated mainly on these topics: - structure of this email, - clustering quality, - backtrace quality, - kerneloops processing. [1] https://retrace.fedoraproject.org/faf/ [2] https://fedoraproject.org/wiki/Features/SimplifiedCrashReporting -- Richard Marko -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: abrt server report: 20121004
On Thu, Oct 04, 2012 at 04:52:19PM +0200, Richard Marko wrote: kernel 220 ▁▂▄▅▇▇█ Nice graphs! What's this about? -- These are the statistics generated by ABRT Server deployed on [1]. We are going to send these reports weekly as they should help developers prioritize their work. We expect them to become more and more accurate as more people will start using new versions of ABRT with simplified reporting [2]. Note that kernel is incorrectly blamed as the most destabilized component as we started handling kerneloops reports only last week. Feedback is really appreciated mainly on these topics: - structure of this email, - clustering quality, - backtrace quality, - kerneloops processing. Feature request: Can you do the same backtrace hashing abrt does, and provide a link to any bugs in bugzilla with the abrt_hash in the whiteboard ? Dave -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: abrt server report: 20121004
On Thu, Oct 04, 2012 at 11:02:43AM -0400, Dave Jones wrote: On Thu, Oct 04, 2012 at 04:52:19PM +0200, Richard Marko wrote: kernel 220 ▁▂▄▅▇▇█ Nice graphs! What's this about? -- These are the statistics generated by ABRT Server deployed on [1]. We are going to send these reports weekly as they should help developers prioritize their work. We expect them to become more and more accurate as more people will start using new versions of ABRT with simplified reporting [2]. Note that kernel is incorrectly blamed as the most destabilized component as we started handling kerneloops reports only last week. Feedback is really appreciated mainly on these topics: - structure of this email, - clustering quality, - backtrace quality, - kerneloops processing. Feature request: Can you do the same backtrace hashing abrt does, and provide a link to any bugs in bugzilla with the abrt_hash in the whiteboard ? Never mind. It seems you do that, and I was looking at reports where no bug had been filed. Perhaps print no bug filed yet in that case ? Dave -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: abrt server report: 20121004
On 10/04/2012 05:00 PM, Peter Robinson wrote: On Thu, Oct 4, 2012 at 3:52 PM, Richard Marko rma...@redhat.com wrote: Hot problems: ID Components Count --- 11834 GConf2 199 11523 control-center 186 Could we make the referenced ID the RHBZ ID for the crash. It makes it more useful for people to cross reference. I have no idea what that ID stands for and for example is 11843 a single problem with GConf2 that has occurred 199 times or is that all the problems for GConf2 added up. The single problem may have more than one attached bugzilla which depends on reports clustered to that single problem. Another issue with using RHBZ ID is that the cluster of related reports may change over time as we get more reports which sometimes leads to splitting/merging of different clusters (problems). So in case of problem ID, ideally, it should represent single issue with the affected component(s) provided that the clustering algorithm works correctly. -- Richard Marko -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: abrt server report: 20121004
On Thu, Oct 04, 2012 at 11:10:47AM -0400, Dave Jones wrote: Feature request: Can you do the same backtrace hashing abrt does, and provide a link to any bugs in bugzilla with the abrt_hash in the whiteboard ? Never mind. It seems you do that, and I was looking at reports where no bug had been filed. Perhaps print no bug filed yet in that case ? Something else just occurred to me, that might be useful, would be to print the top-most function in the summary page. Looking at https://retrace.fedoraproject.org/faf/problems/hot/*/*/kernel/ it would be useful if I could see at a glance that bug 13935 was a wireless bug, without needing to click into it. But... A lot of the 'function' fields on kernel bugs are going to be the same. warn_slowpath_common or warn_slowpath_null. We have a billion WARN() statements all over the kernel, and it's more useful knowing the location of where those are placed than the function name of the WARN statement. Ie, the summary for https://retrace.fedoraproject.org/faf/problems/13955/ should show function: brcms_c_wait_for_tx_completion. There may be a few other function names that would also require similar special casing. Dave -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: abrt server report: 20121004
On Thu, 2012-10-04 at 11:10 -0400, Dave Jones wrote: Feature request: Can you do the same backtrace hashing abrt does, and provide a link to any bugs in bugzilla with the abrt_hash in the whiteboard ? Never mind. It seems you do that, and I was looking at reports where no bug had been filed. Perhaps print no bug filed yet in that case ? Wait, how do we have reports with no bugs? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ABRT Server
On 09/05/2012 07:47 PM, Dave Jones wrote: On Wed, Sep 05, 2012 at 11:39:31AM +0200, Michal Toman wrote: We believe this will help developers to better prioritize their work and make debugging easier (crashes in common libraries are grouped into a single problem, for each crash versions of affected packages/architectures are listed etc.). The 'hot problems' will be very useful for us, as we were just talking last week about reporting such a list upstream periodically. I looked at the only kernel bug caught so far.. https://retrace.fedoraproject.org/faf/reports/452/ 'my_init' isn't part of the kernel package. Could you add some way of filtering out reports from things we don't ship ? Or was this a test-case ? Yes, this was a test-case. Support for kernel oops reporting is not yet in F17, we will add it with the next update. Related: How would I close reports so they don't show up on the list ? Not possible at the moment. For now, server will track associated BZs and close reports automatically. We will add this functionality along with FAS integration. Further related: Clicking 'login' makes this happen.. snip followed by 3-4 pages of additional spew. Debug disabled, we will fix the login URL soon. Thanks for the feedback! -- Richard Marko -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
ABRT Server
Greetings everybody! As you may have noticed, new ABRT 2.0.12 has recently been pushed to Fedora. Besides significant changes in reporting workflow, it also uses the ABRT server to collect what we call uReports (micro-reports). uReport is a short (usually 4kB) fingerprint of the crash, with no private information in it. It contains some basic data (package, architecture, kernel... NO hostname, NO username etc.), together with a debuginfo-less backtrace consisting of binary names, build-ids, function offsets, function names (if available) and some fingerprints helping in duplicate detection. After uploading the uReport to ABRT server, the backtrace is completed - missing function names, source file names and line numbers are added. A clustering algorithm is ran periodically on the reports. It searches for similar uReports and groups them into Problems. We divide these into two categories: 1) Hot problems: started appearing recently and happen often. Should be fixed ASAP. 2) Long-term problems: started appearing long time ago, they do not happen often, but they are still reported sometimes. There are no long-term problems yet, as there is some minimal age limit. After receiving uReport, the server responds whether the problem is already know or not. In the case it is known, the reporting process stops and you can see both Bugzilla URL and ABRT Server URL. Otherwise standard BZ-reporting process continues. You can browse reports and problems through the webUI https://retrace.fedoraproject.org/faf/summary/ We believe this will help developers to better prioritize their work and make debugging easier (crashes in common libraries are grouped into a single problem, for each crash versions of affected packages/architectures are listed etc.). Any feedback or RFEs are welcome [1]! Michal ABRT Team [1] https://fedorahosted.org/abrt/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ABRT Server
On 09/05/2012 02:39 AM, Michal Toman wrote: Greetings everybody! As you may have noticed, new ABRT 2.0.12 has recently been pushed to Fedora. . . . F16, F17, F18, rawhide? Or just F18 rawhide? Or. . . ? -- J. Randall Owens | http://www.ghiapet.net/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ABRT Server
On 09/05/2012 02:44 AM, J. Randall Owens wrote: On 09/05/2012 02:39 AM, Michal Toman wrote: Greetings everybody! As you may have noticed, new ABRT 2.0.12 has recently been pushed to Fedora. . . . F16, F17, F18, rawhide? Or just F18 rawhide? Or. . . ? Partial self-reply: OK, it's definitely in F17, I've had it on mine for almost a week now. -- J. Randall Owens | http://www.ghiapet.net/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ABRT Server
On 05.09.2012 11:44, J. Randall Owens wrote: On 09/05/2012 02:39 AM, Michal Toman wrote: Greetings everybody! As you may have noticed, new ABRT 2.0.12 has recently been pushed to Fedora. . . . F16, F17, F18, rawhide? Or just F18 rawhide? Or. . . ? Ohh, sorry - F17, F18 Rawhide M. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ABRT Server
On Wed, Sep 05, 2012 at 11:39:31AM +0200, Michal Toman wrote: We believe this will help developers to better prioritize their work and make debugging easier (crashes in common libraries are grouped into a single problem, for each crash versions of affected packages/architectures are listed etc.). The 'hot problems' will be very useful for us, as we were just talking last week about reporting such a list upstream periodically. I looked at the only kernel bug caught so far.. https://retrace.fedoraproject.org/faf/reports/452/ 'my_init' isn't part of the kernel package. Could you add some way of filtering out reports from things we don't ship ? Or was this a test-case ? Related: How would I close reports so they don't show up on the list ? Further related: Clicking 'login' makes this happen.. DoesNotExist at /auth/login/ Site matching query does not exist. Request Method: GET Request URL: https://retrace.fedoraproject.org/faf/auth/login/?next=/faf/reports/452/ Django Version: 1.3.1 Exception Type: DoesNotExist Exception Value: Site matching query does not exist. Exception Location: /usr/lib/python2.6/site-packages/django/db/models/query.py in get, line 349 Python Executable: /usr/bin/python Python Version: 2.6.6 Python Path: ['/usr/lib64/python26.zip', '/usr/lib64/python2.6', '/usr/lib64/python2.6/plat-linux2', '/usr/lib64/python2.6/lib-tk', '/usr/lib64/python2.6/lib-old', '/usr/lib64/python2.6/lib-dynload', '/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.3-py2.6-linux-x86_64.egg', '/usr/lib64/python2.6/site-packages', '/usr/lib64/python2.6/site-packages/gtk-2.0', '/usr/lib/python2.6/site-packages', '/usr/lib/python2.6/site-packages/setuptools-0.6c11-py2.6.egg-info'] Server time:Wed, 5 Sep 2012 19:45:33 +0200 followed by 3-4 pages of additional spew. Dave -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ABRT Server
On 05/09/12 19:47, Dave Jones wrote: followed by 3-4 pages of additional spew. Which means somebody has problems with reading comprehension: https://docs.djangoproject.com/en/dev/ref/settings/#debug: DEBUG Default: False A boolean that turns on/off debug mode. Never deploy a site into production with DEBUG turned on. Did you catch that? NEVER deploy a site into production with DEBUG turned on. (and of course in the error page you can find that DEBUG = True) Matěj -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
