From Fedora Project Wiki

(typo)
(Drop direct Test Days category membership)
 
(114 intermediate revisions by 20 users not shown)
Line 1: Line 1:
{{draft}}
{{admon/important|If you can somehow improve quality of this document, please join the fight and help}}
{|border="1"
{|border="1"
|-style="color: white; background-color: #3074c2; border:1px; font-weight: bold"  
|-style="color: white; background-color: #3074c2; border:1px; font-weight: bold"  
| DATE || TIME || WHERE
| DATE || TIME || WHERE
|-
|-
| '''2009-08-20''' || From ''12:00'' to ''21:00'' UTC (8am - 5pm EDT, 14:00 - 23:00 CET) || [irc://irc.freenode.net/fedora-qa #fedora-qa] ([http://webchat.freenode.net/?channels=fedora-qa webirc])
| '''2009-08-20''' || From ''12:00'' to ''21:00'' UTC (8am - 5pm EDT, 14:00 - 23:00 CET) || [irc://irc.freenode.net/fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
|-
|-
|}
|}


== Testing ABRT ==


Today's installment of Fedora Test Day will focus on '''Automated Bug Reporting Tool (ABRT)'''. This tool should help non-power users with bug reporting, making it as easy as a few mouse clicks. ABRT is a daemon that watches for application crashes. When a crash occurs, it collects the crash data (core file, application's command line etc.) and takes action according to the type of application that crashed and according to the configuration in the abrt.conf configuration file.
== What to test? ==
 
Today's installment of Fedora Test Day will focus on '''Automated Bug Reporting Tool ([[Features/ABRT|ABRT]])'''. This tool should help non-power users with bug reporting, making it as easy as a few mouse clicks. [[Features/ABRT|ABRT]] is a daemon that watches for application crashes. When a crash occurs, it collects the crash data (core file, application's command line etc.) and takes action according to the type of application that crashed and according to the configuration in the abrt.conf configuration file.
''Bottom line'': do not hunt the bugs with a pitchforks, rather use bugzappers/big light source to draw them from the dark and [http://fedorapeople.org/~dpravec/AsciiArt/MyBugZappers.html kill them easily at close range].
''Bottom line'': do not hunt the bugs with a pitchforks, rather use bugzappers/big light source to draw them from the dark and [http://fedorapeople.org/~dpravec/AsciiArt/MyBugZappers.html kill them easily at close range].


ABRT should be easy for users and very useful for developers and admins. Ease of crash/bug reporting and quick response from maintainers based on info from ABRT should make Fedora more stable and thus more attractive for users.
[[Features/ABRT|ABRT]] should be easy for users and very useful for developers and admins. Ease of crash/bug reporting and quick response from maintainers based on info from [[Features/ABRT|ABRT]] should make Fedora more stable and thus more attractive for users.
 
We will test:
 
* ABRT GUI;
* compiled (C/C++) programs support;
* Python programs support;
* detection if apps are from supported packages;
* using configured plugins:
** database plugin;
** bugzilla plugin (report crash to bugzilla);
** file transfer plugin (transfer crash data via network);
** mailx plugin (send mail when crash happens);
** kernel oops plugin;
** RunApp plugin (run arbitrary application when crash happens).


== Who's available ==
== Who's available ==


The following people will be available for testing, workarounds, bug fixes, and general discussion:
The following people will be available for testing, workarounds, bug fixes, and general discussion:
* Development - [[User:zprikryl| Zdenek Prikryl]] [[User:jmoskovc| Jiri Moskovcak]] (confirmed) '''<<FIXME: Confirmation needed>>'''
* Development - [[User:zprikryl|Zdeněk Přikryl]] (zprikryl), [[User:jmoskovc|Jiří Moskovčák]] (jmoskovc)
* Quality Assurance - [[User:dpravec| David Pravec]], [[User:kparal| Kamil Páral]], [[User:jlaska| James Laska]]
* Quality Assurance - [[User:dpravec|David Pravec]] (dpravec), [[User:kparal|Kamil Páral]] (kparal), [[User:jlaska|James Laska]] (jlaska), [[User:mnowak|Michal Nowak]] (mnowak)
 
== Prerequisite for Test Day ==
 
You will need to get current ABRT (select your method):
# install latest ABRT from Rawhide
# install latest ABRT from its development repository on Fedora 11
'''<<FIXME: for now we have only internal [[RedHat]] IP server, setup public repository!>>'''. For Redhat internal abrt development server create /etc/yum.repos.d/abrt.repo containing:
 
<pre>
[abrt]
name=ABRT
baseurl=http://10.34.33.153/$releasever/$basearch/
gpgcheck=0
enabled=1
</pre>
# download and burn ABRT Testing CD ([http://fedorapeople.org/~dpravec/testdays/2009-08-20_ABRT/ ISO images] will be available at least 24 hours before the test day starts)


{{admon/important| Note: for reporting to work well, you should have a ''fully-updated system'' (Fedora 11 or Rawhide). Reporting uses <code>-debuginfo</code> packages, which have to match the version of the corresponding crashed program's packages. This also avoids reporting a bug which has already been fixed in a later version of the software. }}
== What's needed to be able to test ==


* A system with some kind of network connection
* '''Fully updated''' Rawhide or Fedora 11 installation  with ABRT installed or special [[#Live_Image|ABRT TestDay Live image]] (i686 or x86_64)


== ABRT Documentation ==
=== How to install ABRT ===
If you do not use the provided LiveCD, but you use your own Fedora 11 or Rawhide installation, you need to install latest ABRT packages by running following commands:
* [https://fedoraproject.org/wiki/Features/ABRTF12 ABRT features, overview]
* [https://fedorahosted.org/abrt/wiki ABRT Home page] (trac wiki)
* [http://fedoraproject.org/w/uploads/a/ab/ABRT.odp ABRT FUDCon Berlin 2009 presentation]
* ABRT was in the past called [[Features/CrashCatcher|CrashCatcher]]


== How to start using ABRT  ==
First add correct repository:
 
* '''Fedora 11:'''
Install abrt and plugins:
<pre># yum install abrt-dekstop</pre>
 
This is not needed when you will use [http://fedorapeople.org/~dpravec/testdays/2009-08-20_ABRT/ ABRT TestDay Live CD].
{{admon/important| After installation of ABRT you should ''reboot'' your computer to have everything working properly.}}
 
Start the daemon (as root):
<pre># /etc/init.d/abrt start</pre>
 
or:
<pre>
<pre>
$ chkconfig abrt on
curl -o /etc/yum.repos.d/abrt.repo  http://jmoskovc.fedorapeople.org/abrt.repo
$ reboot
</pre>
</pre>
 
* '''Rawhide:'''
Start the notification applet (should be autostarted, but if it's not):
<pre>$ abrt-applet &</pre>
 
=== Test basic functionality ===
 
Now if something crashes, ABRT will handle the crash. If you want to  test this, crash something, for example:
<pre>
<pre>
$ xfontsel &
curl -o /etc/yum.repos.d/abrt-rawhide.repo  http://jmoskovc.fedorapeople.org/abrt-rawhide.repo
$ killall -6 xfontsel
</pre>
</pre>


An icon will appear in the notification area.
Now install/update ABRT:
You can now run the GUI:
<pre>
<pre>
$ abrt-gui &
su
rm -f /var/cache/abrt/abrt-db
yum remove kerneloops
yum install abrt-desktop
reboot
</pre>
</pre>


Now select the crash, click "report" to report it, or click "delete" to delete it.
Please do not forget to '''reboot'''. It's needed after installing [[Features/ABRT|ABRT]].


== Test Plan ==
{{admon/tip|ABRT packages were updated|Latest package version is 0.0.7.2-3. If yum doesn't see the update, you have to <code>yum clean all</code>. Restart the service <code>service abrt restart</code> after the update.}}


First let's go thru the config file and explain purpose of every option
=== '''Live Image''' ===
one can find there.....


Let start with common section:
Optionally, you may download a non-destructive rawhide live image for your architecture with latest ABRT pre-installed. Tips on using a live image are available at [[FedoraLiveCD]]. For Fedora on USB flash disk consult [[FedoraLiveCD/USBHowTo]].
<pre>
[ Common ]
# Enable GPG check
# this option is to ensure, that we primary report crashes only in fedora signed packages
# if you disable this abrt will report crashes in customized unsigned packages
EnableOpenGPG = no
</pre>


How to test it:
{|
 
! Architecture !! SHA256
Set this to yes, create some package (or download 3rd party one), install it and crash the program from that package - ABRT should ignore it. Set this to no, crash some program from the unsigned package, this time ABRT should notice it. Rest this with signed Fedora package, it should report the crash in both cases.
|-
 
| [http://dpravec.fedorapeople.org/testdays/2009-08-20_ABRT/testday-20090820_i686-2.iso i686] || <code>635e295f50abf3fc7fc765c658ce68e86428c5812f3ca0e648fa26d33f90cd86</code>
Using GPG Keys:
|-
<pre>
| [http://dpravec.fedorapeople.org/testdays/2009-08-20_ABRT/testday-20090820_x86_64-2.iso x86_64] || <code>542047d8d09a4bd2ec9a8da7e2ac3b17e862ba88e4014aa00c153c7d6ea86622</code>
# this is the place, where user can add other trusted gpg keys used to sign packages
|}
# from some repository (e.g. rpm fusion)
# GPG keys
OpenGPGPublicKeys = /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
</pre>
 
How to test this:
Set gpg check to yes and instal some package from fusion rpm (or any other repo). Crash an application from this package - abrt should ignore it this time. Leave gpg check on and import the gpg key from the repo(if you haven't already). Add the gpg key into abrt config, crash semething from the package - and this time it should be reported.
 
Blacklisting packages:
<pre>
# blacklisted packages
BlackList = bash, bind, apache2
</pre>
 
How to test this: what's in blacklist is ignored, I think this is pretty obvious how to test it
 
ABRT Plugins:
<pre>
# enabled plugins
EnabledPlugins = SQLite3, CCpp, Logger
</pre>
 
How to test this: only plugins in EnabledPlugins are loaded, so try to run <code>$ abrt -d </code> and
you should see what is being loaded and try to fidle with enabled plugins -- if you remove SQLite3 plugin it should complain that it needs some DB plugin.
 
Database Plugin:
<pre>
# selected DB plugin
Database = SQLite3
 
# this option is to ensure, that crashdumps won't take the whole HDD space
MaxCrashReportsSize = 100;
</pre>
 
How to test this: set this to some lower value and try to generate some crashdumps with abrt and
exceed this limit - the last dump shouldn't be saved
note - the last saved dump can exceed this value, but the next one won't
be saved
 
Actions and reporters:
<pre>
# list of actions and reporters which are activated immediately after a
crash
# occurs
ActionsAndReporters =
</pre>
 
If you add here some repotrer or action plugin, then it shout be run at crash time. So for example:
<pre>ActionsAndReporters = RunApp("ls". "ls-output")</pre>
 
Save output from ls command into the file called ls-output. This file will be used in summary report. Try Reporter plugin Mailx(<subject>) or other...,
 
 
Now let's gou through second section. There is saved association among analyzers and actions and/or reporter plugins:
<pre>
[ AnalyzerActionsAndReporters ]
# all C/C++ crashers will be reporter via Logger
CCpp = Logger
# if bind crash. then an email will be send and Logger should be silent
CCpp:bind = Mailx("[abrt] Bind crashed")
# all kernel crashers will be reporter via Logger
Kerneloops = KerneloopsReporter
</pre>
 
How to test this: try to change the analyzer - reporter association to smth else and report some crash.
it should reported somewhere else (Logger logs to /var/log/abrt-logger, mailx sends email to the configured email address)
 
Last section is:
<pre>
[ Cron ]
# hh:mm
# * means every
# every 5 minutes an action plugin Kerneloops will be activated
*:5 = Kerneloops
</pre>
 
How to test: Try to add activation of other action plugin in particular time. Cron should activate it.
 
=== ABRT Test Cases to be tested ===


<!-- Provide a list of test areas or test cases that you'd like contributors to execute.  For other examples, see [[:Category:Test_Cases]].
{{admon/important|Check if you have latest images|There were older images available for some time, but when they have been updated with newer ABRT version, we produced new ones. Please make sure you have the latest image by verifying the checksum (run <code>sha256sum testday-20090820*.iso</code> ). Thanks.}}
-->


Available tests include:
== How to test ==
* [[QA:Testcase_abrt]] - default crash report
* [[QA:Testcase_abrt_Logger]] - Logger plugin
* [[QA:Testcase_abrt_Mailx]] - Mailx plugin


=== Test Cases ===


Some more cases might be in [https://fedoraproject.org/wiki/Category:ABRT_Test_Cases  ABRT_Test_Cases] Category.
Follow each of following [[:Category:ABRT_Test_Cases|ABRT Test Cases]] and sum up the results in the tables below. Report your findings also in [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=abrt Bugzilla] or [https://fedorahosted.org/abrt/report/1 ABRT Trac] (enter FAS username/password). Please provide links to bugreports in results table.
'''<<FIXME: move all tests from this page into this,, update existing ABRT (or CrachCather) Test Cases>>'''


# [[QA:Testcase_ABRT]] - default crash report
# [[QA:Testcase_ABRT_Logger]] - Logger plugin
# [[QA:Testcase_ABRT_Bugzilla]] - Bugzilla plugin
# [[QA:Testcase_ABRT_Mailx]] - Mailx plugin
# [[QA:TestCase ABRT BlackList]] - package blacklist
# [[QA:Testcase ABRT GPG check]] - reporting crashes of signed packages only
# [[QA:TestCase ABRT GPG Keys]] - additional keys for signing packages
# [[QA:Testcase ABRT Actions and Reporters]] - testing of action/reporting plugins
# [[QA:Testcase ABRT Cron]] - periodical plugins using Cron
# [[QA:Testcase ABRT Plugins]] - configuring plugins
# [[QA:Testcase ABRT CLI]] - CLI interface
# [[QA:Testcase ABRT kernel]] - kernel oops
# [[QA:Testcase ABRT python]] - python tracebacks


=== Known issues ===  
=== Known issues ===  


Consult list of [https://fedorahosted.org/abrt/report/1 active tickets] before reporting an issue.  The most common issues are listed below:
Consult list of [https://fedorahosted.org/abrt/report/1 active tickets] before reporting an issue.  The most common issues are listed below:
* '''Report multiple crashes''' - if you want to report same crash twice, you have to remove CC's DB (default path /var/cache/crash-catcher/crash-catcher-db) and make a crash again
* '''Applet (or other icons) in notification area is not visible''' - that's a known bug in Rawhide, please try to run <code>killall notification-area-applet</code> and reload it a few times, it may help
* '''dbus timeout''' - if reporting causes an installation of many debuginfos, then a dbus timeout may occur. In that case, try to report crash again after debuginfos are installed.
* '''Recreate report for same crash''' - if you want to recreate a report of same crash, you have to delete it using button in GUI and make a crash gain
* '''crash-catcher daemon crash''' - if crash-catcher daemon unexpectedly crashs, then look for .lock files in /var/cache/crash-catcher/ and delete them. They may cause a deadlock.
* '''Nothing happened?''' - if it seems to do nothing, try to disable PGP checking and restart daemon
* '''Nothing happened?''' - if it seems to do nothing, try to disable PGP checking and restart daemon
* '''Graphical warnings''' - gui writes some gtk warnings
* '''Graphical warnings''' - gui writes some gtk warnings (it's gtk's fault)
* '''Report editing''' - report editing from gui doesn't work
* '''rpm %requires''' - it needs rpm >= 4.7.0-1
* '''rpm %requires''' - it needs rpm >= 4.6.0-1 (rc3 segfaults)
* ''' bug-buddy or other crash catching tools might take precedence over ABRT''' if you are using them. ABRT will catch only crashes which are not caught by other tools.
* you cannot use abrt to catch crashes of OpenOffice, KDE and Java apps -- they are catching those crashes themselves.
* '''Cannot catch OpenOffice.org, KDE and Java''' - these applications have a built-in method for capturing failures so it is the same as with BugBuddy etc.
* if you're updating from version <= 0.0.5-6 make sure you remove /var/abrt/cache/abrt-db (we've changed the db fomrat and not yet implemented automatic updating mechanism)
* '''if you're updating from version <= 0.0.5-6''' - make sure you remove /var/cache/abrt/abrt-db (we've changed the db format and not yet implemented automatic updating mechanism)'''
'''<<FIXME: Confirmation/cleanup needed>>'''
* '''GUI doesn't inform you about success of failure of a reporting.''' - But you can find results in ABRT's db (default path /var/cache/abrt, it is sqlite3 db, table name is "abrt") - it should be fixed, but in case it's not try to look for these files


== Test Results ==
== Test Results ==


<!-- Construct a table or list to allow testers to post results.  Each column should be a test case or configuration, and each row should consist of test results.  For example: -->
=== Issues that were identified ===


=== Issues that were identified ===
Don't report duplicates, thanks :) Just write a comment to the bugzilla that you have also noticed the bug.


{| border="1px"
{| class="wikitable sortable" border="1"
|-style="color: white; background-color: #3074c2; font-weight: bold"  
! Tester
| Tester || Description || Bug references
! Description
! Bug references
|-
| [[User:kparal]]
| Right click on applet hides the applet but does nothing
| {{bz|518386}}
|-
| [[User:guaneryu]]
| OpenGPGCheck option takes no effect
| {{bz|518396}} CLOSED
|-
| [[User:czhang]]
| testcase #1: no item can be selected after clicked abrt-gui icon if other user's application crashes.
| {{bz|518409}} CLOSED
|-
| [[User:mhlavink]]
| continuous reporting of one kernel oops
| {{bz|518413}}
|-
| [[User:mhlavink]]
| ordinary user's applet shows up for root owned crashes
| {{bz|518420}}
|-
| [[User:mhlavink]]
| abrt silently starts when plugin is configured but not installed
| {{bz|518422}}
|-
| [[User:hdong]]
| testcase #8: CCpp:<APPNAME> doesn't work
| {{bz|518414}} CLOSED
|-
| [[User:azelinka]]
| report window larger that screen (no horizontal scrolling)
| {{bz|518425}} CLOSED
|-
| [[User:azelinka]]
|  bugzilla plugin can't detect correct component for a bug
| {{bz|518438}} CLOSED
|-
| [[User:tpelka]]
|  RunApp do not work - abrt-plugin-runapp installed
| {{bz|518465}} CLOSED
|-
| [[User:vbenes]]
|  cannot use # in bugzilla password
| {{bz|518459}} CLOSED
|-
| [[User:vbenes]]
| crash while scanning syslog
| {{bz| 518472}}
|-
| [[User:vbenes]]
| missing python-sexy dependency
| FIXED no bz
|-
| [[User:dpravec]]
| it would be nice for some admins to be able to catch and process crashes of theirs own compiled (unpackaged, unsigned) applications. Not for Bugzilla plugin, but for some custom reporting/actions.
| Trac [https://fedorahosted.org/abrt/ticket/73 #73]
|-
| [[User:dpravec]]
| when abrt is upgrading from older version, the old database is making it confused. Dont force users to rm the file manually, detect this during upgrade and migrate the database, or just backup it.
| Trac [https://fedorahosted.org/abrt/ticket/74 #74]
|-
| [[User:tpelka]]
| Wouldn't be cool use keyring except plaintext passwords?
| TBD
|-
| [[User:azelinka]]
|  user configuration of plugins doesn't survive service restart
| {{bz|518457}}
|-
| [[User:mnowak|Michal Nowak]]
| abrt-gui allows "sending" report which is not in existing anymore
| Trac [https://fedorahosted.org/abrt/ticket/75 #75]
|-
| [[User:jlaska]]
| Missing %requirse on python-sexy
| {{bz|518488}} -  Missing %requires python-sexy - ImportError: No module named sexy
|-
| [[User:jlaska]]
| /usr/sbin/abrt segfaults on startup (both abrt-0.0.7.1-1.fc12 and abrt-0.0.7.2-3.fc12)
| {{bz|518498}} -  Segmentation fault. 0x006aa95e in two_way_short_needle (needle_len=
|-
| [[User:jlaska]]
| The bugzilla plugin works great, however gdb segfaulted while trying to grab a backtrace from the original failure
| {{bz|FIXME}}
|-
|-
| [[User:FasUser]] || ..... || [http://bugzilla.redhat.com/show_bug.cgi?id=xxx #xxx]
| [[User:jkoten]]
| testcase #8
  CCpp = Logger //logger is not silent for transmission, logs the crash 
  CCpp:transmission = Mailx("[abrt] Transmission")
| {{bz|518606}}
|-
|| [[User:jkoten]]
| testcase #8
  CCpp = Logger, Mailx
  CCpp:transmission = Mailx("[abrt] Transmission") //abrt crashes when reporting transmission crash 
| {{bz|518609}}
|-
|-
|}
|}
Line 245: Line 210:
=== Things that work alright ===
=== Things that work alright ===


{| border="1px"
{| class="wikitable sortable" border="1"
|-style="color: white; background-color: #3074c2; font-weight: bold"  
! Tester  
| Tester || Description
! Description
|-
|-
| [[User:FasUser]] || ..............
| [[User:guaneryu]]  
|
*1. Followed the testcase description, got the expected result
*2. Followed the testcase description, got the expected result
*3. Followed the testcase description, got the expected result
*4. Followed the testcase description, got the expected result
*5. Followed the testcase description, got the expected result
*9. Followed the testcase description, added "5 = Logger" at the [cron] section, got expected result from "abrt -d" output
*10.Followed the testcase description, changed "MaxCrashReportsSize" to 0 and no crash could be detected
*11.Followed the testcase description, got the expected result
*12.Followed the testcase description, got the expected result from command line, and abrt-applet popped up a notification but no items listed in abrt-gui
|-
| [[User:kparal]]
| testcase #1 worked ok
|-
| [[User:hdong]]
|
*1.Testcase_ABRT            get expected results, but some crashed process icon miss in abrt-gui item list, others show
*2.Testcase_ABRT_Logger    PASS
*3.Testcase_ABRT_Bugzilla  PASS
*4.Testcase_ABRT_Mailx      PASS
*5.TestCase ABRT BlackList  PASS
*9.Testcase ABRT Cron      PASS
*10.Testcase ABRT Plugins  get expected results, set MaxCrashReportsSize to 0，no crash could be detected
*11.Testcase ABRT CLI      PASS
*12.Testcase ABRT kernel    get expected results, abrt-applet poped up the notification but no items listed in abrt-gui
|-
| [[User:czhang]]
| testcase #2~#5, #9~#12 work as what expected.
|-
| [[User:twaugh]] || Catching Python traceback
|-
| [[User:mvadkert]]
| testcase #2~#5 work as what expected.
|-
| [[User:vbenes]]
|
* testcase #1 PASS
* testcase #2 PASS
* testcase #3 PASS
* testcase #4 PASS
* testcase #5 PASS
* testcase #6 N/A
* testcase #7 N/A
* testcase #8 TBD
* testcase #9 TBD
* testcase #10 PASS
* testcase #11 TBD
* testcase #12 TBD
* testcase #13 TBD
|-
| [[User:jlaska]]
| PASS ([[QA:Testcase_ABRT_Bugzilla]], [[QA:Testcase_ABRT_Logger]])
|-
| [[User:jkoten]]
|
* testcases #1 - #5; #9 - #13 PASS 
* testcase #8 Partial success - ActionsAndReporters = Mailx("[abrt] !!!!crash was detected!!!!!"), Logger, RunApp("ls", "ls-output") // works as expected - plugins were activated immediately after a crash occurs.
|-
|-
|}
|}


 
  [[Category:Fedora 12 Test Days]]
{{admon/warning| TODO: some tools/scripts/icons for users to help with testing. Let the user easily monitor what is going on, or give him some tools so he can test ABRT even without command line tools. Or is this a bad idea? Please help us with this!}}
 
{{admon/warning| TODO: should users during ABRT test day report bugs directly into [[Bugzilla]]? How can we delete all such "bugs" later if they will eat too much space? Or will we use another Bugzilla? Where? How? ? Who can help?}}
 
[[Category:Test Days]]
 
[[Category:Draft_documentation]]

Latest revision as of 19:32, 26 June 2015

DATE TIME WHERE
2009-08-20 From 12:00 to 21:00 UTC (8am - 5pm EDT, 14:00 - 23:00 CET) #fedora-test-day (webirc)


What to test?[edit]

Today's installment of Fedora Test Day will focus on Automated Bug Reporting Tool (ABRT). This tool should help non-power users with bug reporting, making it as easy as a few mouse clicks. ABRT is a daemon that watches for application crashes. When a crash occurs, it collects the crash data (core file, application's command line etc.) and takes action according to the type of application that crashed and according to the configuration in the abrt.conf configuration file. Bottom line: do not hunt the bugs with a pitchforks, rather use bugzappers/big light source to draw them from the dark and kill them easily at close range.

ABRT should be easy for users and very useful for developers and admins. Ease of crash/bug reporting and quick response from maintainers based on info from ABRT should make Fedora more stable and thus more attractive for users.

Who's available[edit]

The following people will be available for testing, workarounds, bug fixes, and general discussion:

What's needed to be able to test[edit]

  • A system with some kind of network connection
  • Fully updated Rawhide or Fedora 11 installation with ABRT installed or special ABRT TestDay Live image (i686 or x86_64)

How to install ABRT[edit]

If you do not use the provided LiveCD, but you use your own Fedora 11 or Rawhide installation, you need to install latest ABRT packages by running following commands:

First add correct repository:

  • Fedora 11:
curl -o /etc/yum.repos.d/abrt.repo  http://jmoskovc.fedorapeople.org/abrt.repo
  • Rawhide:
curl -o /etc/yum.repos.d/abrt-rawhide.repo  http://jmoskovc.fedorapeople.org/abrt-rawhide.repo

Now install/update ABRT: 

su
rm -f /var/cache/abrt/abrt-db
yum remove kerneloops 
yum install abrt-desktop
reboot

Please do not forget to reboot. It's needed after installing ABRT.

ABRT packages were updated
Latest package version is 0.0.7.2-3. If yum doesn't see the update, you have to yum clean all. Restart the service service abrt restart after the update.

Live Image[edit]

Optionally, you may download a non-destructive rawhide live image for your architecture with latest ABRT pre-installed. Tips on using a live image are available at FedoraLiveCD. For Fedora on USB flash disk consult FedoraLiveCD/USBHowTo.

Architecture SHA256
i686 635e295f50abf3fc7fc765c658ce68e86428c5812f3ca0e648fa26d33f90cd86
x86_64 542047d8d09a4bd2ec9a8da7e2ac3b17e862ba88e4014aa00c153c7d6ea86622
Check if you have latest images
There were older images available for some time, but when they have been updated with newer ABRT version, we produced new ones. Please make sure you have the latest image by verifying the checksum (run sha256sum testday-20090820*.iso ). Thanks.

How to test[edit]

Test Cases[edit]

Follow each of following ABRT Test Cases and sum up the results in the tables below. Report your findings also in Bugzilla or ABRT Trac (enter FAS username/password). Please provide links to bugreports in results table.

  1. QA:Testcase_ABRT - default crash report
  2. QA:Testcase_ABRT_Logger - Logger plugin
  3. QA:Testcase_ABRT_Bugzilla - Bugzilla plugin
  4. QA:Testcase_ABRT_Mailx - Mailx plugin
  5. QA:TestCase ABRT BlackList - package blacklist
  6. QA:Testcase ABRT GPG check - reporting crashes of signed packages only
  7. QA:TestCase ABRT GPG Keys - additional keys for signing packages
  8. QA:Testcase ABRT Actions and Reporters - testing of action/reporting plugins
  9. QA:Testcase ABRT Cron - periodical plugins using Cron
  10. QA:Testcase ABRT Plugins - configuring plugins
  11. QA:Testcase ABRT CLI - CLI interface
  12. QA:Testcase ABRT kernel - kernel oops
  13. QA:Testcase ABRT python - python tracebacks

Known issues[edit]

Consult list of active tickets before reporting an issue. The most common issues are listed below:

  • Applet (or other icons) in notification area is not visible - that's a known bug in Rawhide, please try to run killall notification-area-applet and reload it a few times, it may help
  • Recreate report for same crash - if you want to recreate a report of same crash, you have to delete it using button in GUI and make a crash gain
  • Nothing happened? - if it seems to do nothing, try to disable PGP checking and restart daemon
  • Graphical warnings - gui writes some gtk warnings (it's gtk's fault)
  • rpm %requires - it needs rpm >= 4.7.0-1
  • bug-buddy or other crash catching tools might take precedence over ABRT if you are using them. ABRT will catch only crashes which are not caught by other tools.
  • Cannot catch OpenOffice.org, KDE and Java - these applications have a built-in method for capturing failures so it is the same as with BugBuddy etc.
  • if you're updating from version <= 0.0.5-6 - make sure you remove /var/cache/abrt/abrt-db (we've changed the db format and not yet implemented automatic updating mechanism)
  • GUI doesn't inform you about success of failure of a reporting. - But you can find results in ABRT's db (default path /var/cache/abrt, it is sqlite3 db, table name is "abrt") - it should be fixed, but in case it's not try to look for these files

Test Results[edit]

Issues that were identified[edit]

Don't report duplicates, thanks :) Just write a comment to the bugzilla that you have also noticed the bug.

Tester Description Bug references
User:kparal Right click on applet hides the applet but does nothing RHBZ #518386
User:guaneryu OpenGPGCheck option takes no effect RHBZ #518396 CLOSED
User:czhang testcase #1: no item can be selected after clicked abrt-gui icon if other user's application crashes. RHBZ #518409 CLOSED
User:mhlavink continuous reporting of one kernel oops RHBZ #518413
User:mhlavink ordinary user's applet shows up for root owned crashes RHBZ #518420
User:mhlavink abrt silently starts when plugin is configured but not installed RHBZ #518422
User:hdong testcase #8: CCpp:<APPNAME> doesn't work RHBZ #518414 CLOSED
User:azelinka report window larger that screen (no horizontal scrolling) RHBZ #518425 CLOSED
User:azelinka bugzilla plugin can't detect correct component for a bug RHBZ #518438 CLOSED
User:tpelka RunApp do not work - abrt-plugin-runapp installed RHBZ #518465 CLOSED
User:vbenes cannot use # in bugzilla password RHBZ #518459 CLOSED
User:vbenes crash while scanning syslog RHBZ # 518472
User:vbenes missing python-sexy dependency FIXED no bz
User:dpravec it would be nice for some admins to be able to catch and process crashes of theirs own compiled (unpackaged, unsigned) applications. Not for Bugzilla plugin, but for some custom reporting/actions. Trac #73
User:dpravec when abrt is upgrading from older version, the old database is making it confused. Dont force users to rm the file manually, detect this during upgrade and migrate the database, or just backup it. Trac #74
User:tpelka Wouldn't be cool use keyring except plaintext passwords? TBD
User:azelinka user configuration of plugins doesn't survive service restart RHBZ #518457
Michal Nowak abrt-gui allows "sending" report which is not in existing anymore Trac #75
User:jlaska Missing %requirse on python-sexy RHBZ #518488 - Missing %requires python-sexy - ImportError: No module named sexy
User:jlaska /usr/sbin/abrt segfaults on startup (both abrt-0.0.7.1-1.fc12 and abrt-0.0.7.2-3.fc12) RHBZ #518498 - Segmentation fault. 0x006aa95e in two_way_short_needle (needle_len=
User:jlaska The bugzilla plugin works great, however gdb segfaulted while trying to grab a backtrace from the original failure RHBZ #FIXME
User:jkoten testcase #8 
 CCpp = Logger //logger is not silent for transmission, logs the crash   
 CCpp:transmission = Mailx("[abrt] Transmission")
RHBZ #518606
User:jkoten testcase #8 
 CCpp = Logger, Mailx 
 CCpp:transmission = Mailx("[abrt] Transmission") //abrt crashes when reporting transmission crash
RHBZ #518609

Things that work alright[edit]

Tester Description
User:guaneryu
  • 1. Followed the testcase description, got the expected result
  • 2. Followed the testcase description, got the expected result
  • 3. Followed the testcase description, got the expected result
  • 4. Followed the testcase description, got the expected result
  • 5. Followed the testcase description, got the expected result
  • 9. Followed the testcase description, added "5 = Logger" at the [cron] section, got expected result from "abrt -d" output
  • 10.Followed the testcase description, changed "MaxCrashReportsSize" to 0 and no crash could be detected
  • 11.Followed the testcase description, got the expected result
  • 12.Followed the testcase description, got the expected result from command line, and abrt-applet popped up a notification but no items listed in abrt-gui
User:kparal testcase #1 worked ok
User:hdong
  • 1.Testcase_ABRT get expected results, but some crashed process icon miss in abrt-gui item list, others show
  • 2.Testcase_ABRT_Logger PASS
  • 3.Testcase_ABRT_Bugzilla PASS
  • 4.Testcase_ABRT_Mailx PASS
  • 5.TestCase ABRT BlackList PASS
  • 9.Testcase ABRT Cron PASS
  • 10.Testcase ABRT Plugins get expected results, set MaxCrashReportsSize to 0，no crash could be detected
  • 11.Testcase ABRT CLI PASS
  • 12.Testcase ABRT kernel get expected results, abrt-applet poped up the notification but no items listed in abrt-gui
User:czhang testcase #2~#5, #9~#12 work as what expected.
User:twaugh Catching Python traceback
User:mvadkert testcase #2~#5 work as what expected.
User:vbenes
  • testcase #1 PASS
  • testcase #2 PASS
  • testcase #3 PASS
  • testcase #4 PASS
  • testcase #5 PASS
  • testcase #6 N/A
  • testcase #7 N/A
  • testcase #8 TBD
  • testcase #9 TBD
  • testcase #10 PASS
  • testcase #11 TBD
  • testcase #12 TBD
  • testcase #13 TBD
User:jlaska PASS (QA:Testcase_ABRT_Bugzilla, QA:Testcase_ABRT_Logger)
User:jkoten
  • testcases #1 - #5; #9 - #13 PASS
  • testcase #8 Partial success - ActionsAndReporters = Mailx("[abrt] !!!!crash was detected!!!!!"), Logger, RunApp("ls", "ls-output") // works as expected - plugins were activated immediately after a crash occurs.
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:2009-08-20_ABRT&oldid=416613"