Fedora Test Days | |
---|---|
ABRT & libreport | |
Date | 2011-09-26 |
Time | all day |
Website | ABRT homepage |
IRC | #fedora-test-day (webirc) |
Mailing list | test |
What to test?
Today's instalment of Fedora Test Day will focus on Automated Bug Reporting Tool (ABRT) and Unified Problem Reporting UI (libreport).
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Jiří Moskovčák (jmoskovc), Nikola Pajkovsky (npajkovs), Denys Vlasenko (dvlasenk), Karel Klíč (kklic), Michal Toman (mtoman)
- Quality Assurance - Richard Marko (rmarko)
Prerequisite for Test Day
- Physical machine or a virtual machine
- An updated Fedora 16 pre-release
How to test?
Update your machine
If you're running Fedora 16, make sure you have all the current updates for it installed, using the update manager.
Live image
You may download a non-destructive Fedora 16 live image for your architecture. Tips on using a live image are available at FedoraLiveCD.
Download the nightly Fedora 16 build for your architecture (choose the desktop spin).
Get latest abrt/libreport packages
The latest versions are:
libreport-2.0.5.981-0.fc16 abrt-2.0.4.981-1.fc16
- in case these are not available in the official repo, use this repo.
Use the following command to install/udpate all of them:
yum -y install --enablerepo=updates-testing abrt abrt-addon-ccpp abrt-addon-kerneloops abrt-addon-python abrt-desktop abrt-gui abrt-libs abrt-cli abrt-retrace-client libreport libreport-cli libreport-gtk libreport-newt libreport-python libreport-plugin-mailx libreport-plugin-logger libreport-plugin-bugzilla libreport-plugin-kerneloops libreport-plugin-reportuploader
Make sure abrtd and abrt-ccpp services are running:
# service abrtd start Starting abrtd (via systemctl): [ OK ] # service abrt-ccpp start Starting abrt-ccpp (via systemctl): [ OK ]
- File
/proc/sys/kernel/core_pattern
contains following output:
# cat /proc/sys/kernel/core_pattern |/usr/libexec/abrt-hook-ccpp %s %c %p %u %g %t e
To be able to use the retrace server feature you have to edit the configuration and change its URL to retrace02.fedoraproject.org
. To do so, open abrt-gui
and go to Edit->Preferences->Retrace Server and change the URL to retrace02.fedoraproject.org
and write insecure to insecure option entry.
Testing
Follow each of these 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 CLI - CLI interface
- QA:Testcase ABRT kernel - kernel oops
- QA:Testcase ABRT vmcore - kernel oops
- QA:Testcase ABRT python - python tracebacks
- QA:Testcase Libreport sealert - sealert integration
- QA:Testcase Libreport anaconda - anaconda integration
- QA:Testcase Libreport firstboot - firstboot integration
- QA:Testcase Retrace Server CLI - Retrace Server CLI
- QA:Testcase Retrace Server GUI - Retrace Server in ABRT GUI
Test Results
If you have problems with any of the tests, report a bug to Bugzilla usually for the component abrt, or libreport for bugs in the libreport library. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the result template to enter your result, as shown in the example result line.
Abrt test cases
Integration test cases
User | sealert | anaconda | firstboot | Retrace cli | Retrace gui | References |
---|---|---|---|---|---|---|
Sample User | ||||||
Vít Ondruch | ||||||
Richard Marko | ||||||
Jiří Moskovčák | ||||||
Karel Klic | ||||||
Michal Toman |