| Fedora Test Days | |
|---|---|
| |
| ABRT | |
| Date | 2015-04-14 |
| Time | all day |
| Website | QA/Fedora_22_test_days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
What to test?
Today's instalment of Fedora Test Day will focus on ABRT
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Jakub Filák (jfilak), Marek Brýša (mbrysa), Matěj Habrnál (mhabrnal), Richard Marko (impure_hate)
- Quality Assurance - ??
Prerequisite for Test Day
List any prerequisite needs for the test event.
- Physical machine or a virtual machine
- An updated Fedora 22 pre-release, Rawhide (tips on installing Rawhide below), or a nightly live image
How to test?
Update your machine
If you're running Fedora 22, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:
Live image
Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.
Get latest abrt/libreport packages
The latest versions are:
satyr-0.16-1.fc22 libreport-2.5.1-1.fc22 abrt-2.5.1-1.fc22 gnome-abrt-1.1.1-1.fc22
Use the following command to install/update all of them:
yum -y install --enablerepo=updates-testing \ abrt abrt-addon-ccpp abrt-addon-kerneloops abrt-addon-python abrt-addon-vmcore abrt-addon-xorg \ abrt-desktop abrt-dbus abrt-gui abrt-libs abrt-cli abrt-retrace-client abrt-plugin-bodhi abrt-tui \ libreport libreport-compat libreport-filesystem libreport-cli libreport-gtk libreport-newt libreport-web \ libreport-python libreport-plugin-mailx libreport-plugin-logger libreport-plugin-bugzilla \ libreport-plugin-kerneloops libreport-plugin-reportuploader libreport-plugin-rhtsupport libreport-plugin-ureport \ satyr gnome-abrt
If these packages are not available in the official Fedora 22 repositories yet, please enable this COPR repository and run the command above: https://copr.fedoraproject.org/coprs/jfilak/abrt-test-day/
Make sure that:
- abrtd and abrt-ccpp services are running:
# systemctl start abrtd.service # systemctl status abrtd.service # systemctl start abrt-ccpp.service # systemctl status abrt-ccpp.service
- file
/proc/sys/kernel/core_patterncontains following output:
# cat /proc/sys/kernel/core_pattern |/usr/libexec/abrt-hook-ccpp %s %c %p %u %g %t e
Test Cases
New and important features
Basic functionality
- QA:Testcase_ABRT - Basic test
- 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 python - python tracebacks
- QA:Testcase ABRT vmcore - kernel oops
- QA:Testcase ABRT cnotify - console notification
- QA:Testcase ABRT Reporting Known Crash - reporting of known crash
- QA:Testcase ABRT ruby gem - ruby exceptions
- QA:Testcase GNOME ABRT MAIN - gnome-abrt
- QA:Testcase ABRT Configuration Storage - configuration storage
- QA:Testcase ABRT SELinux - ABRT GUI now catches AVC messages, too
- QA:Testcase ABRT Knowledgebase - ABRT provides more information about common problems
- QA:Testcase ABRT server - ABRT server user experience
Test Results
If you have problems with any of the tests, report a bug to Bugzilla usually for the component abrt, or gnome-abrt for bugs in the ABRT graphical front end itself. 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.
| User | Hardware | Reporting known crash | Ruby exceptions | Gnome ABRT | Configuration storage | SELinux alerts | Knowledgebase | ABRT server user experience | References |
|---|---|---|---|---|---|---|---|---|---|
| Sample User | KVM/Qemu |  |
 |
 |
|
|
|