From Fedora Project Wiki

No edit summary
Line 129: Line 129:
| {{result|pass}} <ref>Instructions about configuration of the abrt_event.conf and mailx plugin (Mailx.conf file needs to be created because it doesn't exist) are incomplete.</ref>
| {{result|pass}} <ref>Instructions about configuration of the abrt_event.conf and mailx plugin (Mailx.conf file needs to be created because it doesn't exist) are incomplete.</ref>
| {{result|pass}}
| {{result|pass}}
| {{result|inprogress}}
| {{result|warn}} <ref>There is no "Edit->Plugins", probably "Edit->Event configuration" was meant and it worked as expected.</ref>
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}}

Revision as of 12:20, 31 March 2011

Fedora Test Days
}}}
ABRT 2 + Retrace Server
Date 2011-03-31
Time all day
Website https://fedorahosted.org/abrt/
IRC #fedora-test-day (webirc)
Mailing list test


What to test?

Today's installment of Fedora Test Day will focus on Retrace Server and Automated Bug Reporting Tool (ABRT).

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 - Michal Nowak (mnowak)

Prerequisite for Test Day

You will need either fully updated Fedora 15 system or a LiveCD image (download desktop spin).

If your system doesn't boot
There is currently some problem with SELinux that prevents system from booting on fully updated Fedora 15 installation. If that happens to you, add enforcing=0 on kernel boot line in GRUB and the system should boot fine.

How to test?

Prior to test:

  • Fully update ABRT packages (even when running from LiveCD):
# yum update 'abrt*' --enablerepo=updates-testing
  • 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 /var/spool/abrt %s %c %p %u %g %t %h %e 636f726500

Please follow each of following ABRT test cases and sum up the results in the table below:

  1. QA:Testcase ABRT CCPP addon - C/C++ tracebacks
  2. QA:Testcase ABRT python - python tracebacks
  3. QA:Testcase ABRT kernel - kernel oops
  4. QA:TestCase ABRT BlackList - package blacklist
  5. QA:Testcase ABRT quota - limiting the space occupied by ABRT's cache
  6. QA:Testcase ABRT Bugzilla - Bugzilla plugin
  7. QA:Testcase ABRT Logger - Logger plugin
  8. QA:Testcase ABRT Mailx - Mailx plugin
  9. QA:Testcase ABRT SOSreport plugin - sosreport integration with ABRT
  10. QA:Testcase ABRT GUI MAIN - testing the GUI (probably already during the previous steps, so just to sum it up)
  11. QA:Testcase ABRT CLI - CLI interface
  12. QA:Testcase ABRT GUI Localized - exploring localized GUI
  13. QA:Testcase ABRT CLI Localized - exploring localized CLI
  14. QA:Testcase Retrace Server CLI - Retrace Server CLI
  15. QA:Testcase Retrace Server GUI - Retrace Server in ABRT GUI
  16. QA:Testcase ABRT third party event extension - event configuration
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 suggestions about UI, send them via email to developers and/or create a bug report.

Please report all bugs into Bugzilla against the abrt component and Fedora 15 release.

User CCPP python kernel Blacklist quota Bugzilla Logger Mailx sosreport GUI CLI GUI L10N CLI L10N RS CLI RS GUI 3rd-party References
Sample User
none
Warning warn
[1]
Fail fail
[2]
none
none
none
Pass pass
Pass pass
none
none
none
Pass pass
Pass pass
none
none
none
  1. ↑ Test pass, but also encountered RHBZ #54321
  2. ↑ RHBZ #12345
Jaroslav Škarvada
Warning warn
[1]

[2] [3] [4]

Pass pass
Warning warn
[5]
Fail fail
Pass pass
Pass pass
[6]
Pass pass
Pass pass
[7]
Pass pass
Warning warn
[8]
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
  1. ↑ Got message: Need writable directory, but '/var/spool/abrt/ccpp-2011-03-31-11:52:18-1939' is not writable. Move it to '/home/yarda/.abrt/spool' and operate on the moved copy?
    But:
    # rpm -V abrt
    .....UGM. /var/run/abrt
  2. ↑ Got many: Certificate is signed by an untrusted issuer: 'E=mtoman@redhat.com,CN =retrace01.fedoraproject.org,OU=BaseOS,O=Red Hat,L=Brno,C=CZ'.
  3. ↑ There is no "Open ABRT" button, only "Show".
  4. ↑ Got message: Missing separate debuginfo for Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/45/190d029703ca464ad5c5eb6b7f99426a51a2e3
  5. ↑ There was no notification after the /var/log/messages modification.
  6. ↑ Passed, but the UI is ugly and confusing, e.g. I would like to be able to enter the bugzilla credentials (or create new account) after clicking the last confirmation button.
  7. ↑ Instructions about configuration of the abrt_event.conf and mailx plugin (Mailx.conf file needs to be created because it doesn't exist) are incomplete.
  8. ↑ There is no "Edit->Plugins", probably "Edit->Event configuration" was meant and it worked as expected.
David Kutalek
Warning warn
[1] [2]
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
  1. ↑ RHBZ #692428 - Report button in warning inside KDE info area does not work
  2. ↑ RHBZ #692433 - Cannot connect to Gnome keyring daemon dialog becomes annoying
Vít Ondruch
Warning warn
[1]

[2] [3]

Pass pass
Warning warn

[4] [5]

Fail fail

[6]

Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
  1. ↑ Same experience as jskarvad
  2. ↑ RHBZ #692442 - Hi res image for "bug-reporting-window" and task switcher
  3. ↑ RHBZ #692444 - "bug-reporting-window" should be shown as "part of the application"
  4. ↑ abrt_event.conf does not contain the events mentioned in test case
  5. ↑ abrt.conf contains -drwx instead of -drw
  6. ↑ RHBZ #692465 - Blacklist doesn't work
kparal
Pass pass
Fail fail
[1]
none
none
none
none
none
none
none
none
none
none
none
none
none
none
  1. ↑ "abrtd: New dump directory /var/spool/abrt/pyhook-..., processing" in messages, but nothing happens.
Michal Nowak
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:2011-03-31_ABRT_Retrace_Server&oldid=229977"