From Fedora Project Wiki

No edit summary
Line 25: Line 25:

* Physical machine or a virtual machine
* Physical machine or a virtual machine
* An updated [ Fedora 17 pre-release]
* Fedora 17 TC1 []
* Or an updated [ Fedora 17 pre-release]

=== How to test? ===
=== How to test? ===
Line 62: Line 63:
|/usr/libexec/abrt-hook-ccpp %s %c %p %u %g %t e
|/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 {{command|}}. To do so, open {{command|abrt-gui}} and go to ''Edit->Preferences->Retrace Server'' and change the URL to {{command|}} and write '''insecure''' to insecure option entry.
{{admon/warning|Temporary retrace server|As this is only a temporary state and '''insecure''' option is required for the second server to work it's not a good idea to use coredumps that may contain sensitive data. The second server will replace main server soon.}}

==== Testing ====
==== Testing ====

Revision as of 13:22, 25 April 2012

Fedora Test Days
ABRT & Backtrace Deduplication

Date 2012-04-26
Time all day

Website QA/Fedora_17_test_days
IRC #fedora-test-day (webirc)
Mailing list test

Can't make the date?
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 Automated Bug Reporting Tool (ABRT) and Backtrace Deduplication service

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day

How to test?

Update your machine

If you're running Fedora 17, make sure you have all the current updates for it installed, using the update manager.

Live image

You may download a non-destructive Fedora 17 live image for your architecture. Tips on using a live image are available at FedoraLiveCD.

Download the nightly Fedora 17 build for your architecture (choose the desktop spin).

Get latest abrt/libreport packages

The latest versions are: abrt-2.0.10-1.fc17 libreport-2.0.10-2.fc17 - in case these are not available in the official repo, Download them from Koji: abrt libreport

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


Follow each of these test cases:

  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 CLI - CLI interface
  6. QA:Testcase ABRT kernel - kernel oops
  7. QA:Testcase ABRT vmcore - kernel oops
  8. QA:Testcase ABRT python - python tracebacks
  9. QA:Testcase Libreport sealert - sealert integration
  10. QA:Testcase Libreport anaconda - anaconda integration
  11. QA:Testcase Libreport firstboot - firstboot integration
  12. QA:Testcase Retrace Server CLI - Retrace Server CLI
  13. QA:Testcase Retrace Server GUI - Retrace Server in ABRT GUI
Close all fake bugs you create!
During certain test cases you will be required to simulate application crashes and report these crashes into Bugzilla. It is very important that after every such fake report you open the link provided by ABRT and close that bug as NOTABUG with comment like "ABRT testing bug". Otherwise you would overload package developers with fake bug reports. Thank you.
Report SELinux denials against ABRT
If you encounter some SELinux (AVC) denials during testing, please report them against the abrt package, not selinux package. Thanks.

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

User Basic test Logger reporting Bugzilla reporting Mailx plugin CLI interface Kernel oops Python crash Kernel panic(vmcore) References
Sample User
Pass pass
Warning warn
Fail fail
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345

Integration test cases

User sealert anaconda firstboot Retrace cli Retrace gui References
Sample User
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress