From Fedora Project Wiki

(Move long comments to a separate section at end of page)
(Drop direct Test Days category membership)
 
Line 310: Line 310:
<references group="long" />
<references group="long" />


[[Category:Test Days]] [[Category:Fedora 15 Test Days]]
[[Category:Fedora 15 Test Days]]

Latest revision as of 19:37, 26 June 2015

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?[edit]

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

Who's available[edit]

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[edit]

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?[edit]

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[edit]

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
[long 1]

[long 2] [1] [long 3]

Pass pass
Warning warn
[2]
Fail fail
Pass pass
Pass pass
[long 4]
Pass pass
Pass pass
[long 5]
Pass pass
Warning warn
[3]
Pass pass
[long 6]

[4]

Fail fail
[long 7]
Fail fail
[5]
Pass pass
[6]
Pass pass
Pass pass
  1. There is no "Open ABRT" button, only "Show".
  2. There was no notification after the /var/log/messages modification.
  3. There is no "Edit->Plugins", probably "Edit->Event configuration" was meant and it worked as expected.
  4. In this test case several instructions are misplaced to "Expected results".
  5. A lot of messages are not localized to cs_CZ, e.g. "is not writable", "Choose option", "Analyzing coredump" and much much more.
  6. It is not clear from the testcase where "batch" command stores downloaded data.
David Kutalek
Warning warn
[1] [2]
Pass pass
Pass pass
[3] [4]
Warning warn
[5]
Pass pass
Fail fail
[6]
Pass pass
[7] [8]
Pass pass
Pass pass
Warning warn
[9]
Pass pass
[10]
Warning warn
[long 8]
Warning warn
[11]
Pass pass
Warning warn
[12]
Pass pass
  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
  3. Event settings for kernel opps is located in /etc/abrt/events.d/koops_events.conf
  4. abrt-dump-opps log scanner has parameters -drwx (not -drw)
  5. [1]
  6. RHBZ #692574 - Not possible to report to bugzilla without gnome keyring
  7. By default on Live CD there is this action: abrt-action-print -o "${Log_File:-/tmp/abrt.log}" -a "${Append:-no}"
  8. Again because of missing gnome keyring, it is not possible to alter event config in gui.
  9. RHBZ #692803 - Bad integration with KDE - without gnome-keyring - see above
  10. Works, but after reporting using logger and/or Mailx, crash is not marked as reported. Same for GUI. Is it intended?
  11. Again some messages not translated
  12. RHBZ #692802 - Missing debuginfo for fedora15/sleep crash on abrt retrace server
Vít Ondruch
Warning warn
[1]

[2] [3]

Pass pass
Warning warn

[4] [5]

Fail fail

[6]

Warning warn

[7]

Pass pass

[long 9]

Pass pass
Fail fail

[8]

Warning warn

[9]

  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
  7. RHBZ #692474 - Exceeded quota is not reported
  8. I have not /var/cache/abrt directory on my system. Even if I create one, nothing appears in there.
  9. RHBZ #692516 - The ABRT icon is almost invisible in panel
kparal
Pass pass
Pass pass
none
none
none
none
none
none
none
none
none
none
none
none
none
none
Michal Nowak
Pass pass
[1]
Pass pass
[2]
Pass pass

[3] [4]

Fail fail
[5]
Pass pass
Pass pass
[long 10]
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
[6]
Warning warn
[7]
Warning warn
[8]
Pass pass
Pass pass
Pass pass
Other issues

[9] [10]

Luigi Votta
Warning warn
[1]
Warning warn
[2]
Pass pass
Warning warn
[3]
Warning warn
[4]
Fail fail
[5]
  1. Same problema as jskarvad
  2. Unable to catch in abrt the python error
  3. It doesn't seem working
  4. Same as previous RHBZ #692474
  5. cannot retrieve debug-info from repo as in RHBZ #681281
G.Wolfe Woodbury
Pass pass
Pass pass
none
none
none
Pass pass
none
none
none
Pass pass
[1]
none
none
none
none
Warning warn
[2]
none
  1. RHBZ #692549 RHBZ #692554 RHBZ #692557 real bugs
  2. lots of PENDING notices, retreated to local gdb
Honza Horak
Warning warn
[1][long 11]
Warning warn
[2]
Pass pass
Fail fail
[3]
Warning warn
[4]
Warning warn
[5]
Pass pass
Pass pass
Fail fail
[6]
Warning warn
[7]
Pass pass
none
none
none
none
none
  1. Got message: Need writable directory, but /var/spool/abrt/ccpp-...10080/ is not writable
  2. Empty login or password, please check /etc/abrt/plugins/Bugzilla.conf.. But there is both set, but not in abrt-gui.
  3. I still see strace's report when killing "strace sleep 5m".
  4. I see no notification about quota (maybe I cannot run applet).
  5. I cannot log in using manual edit of /etc/abrt/plugins/Bugzilla.conf, but it works using editting in abrt-gui.
  6. There is no "/var/cache/abrt/" at all.
  7. I see no siren logo in F15 - maybe not ABRT issue.
User CCPP python kernel Blacklist quota Bugzilla Logger Mailx sosreport GUI CLI GUI L10N CLI L10N RS CLI RS GUI 3rd-party References

Long comments[edit]

  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. Got message: Missing separate debuginfo for Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/45/190d029703ca464ad5c5eb6b7f99426a51a2e3
  4. 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.
  5. 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.
  6. I would prefer to be able to select reporter by e.g. number (or combination of numbers) and not to cycle Y/N through all available reporters.
  7. It is not fully localized to cs_CZ, e.g. "Problem", "Last Occurence", "Online Help", "Event Configuration" (and all strings in this dialog) strings are not localized.
  8. Not fully translated to Czech, but according to link to translation service, missing pieces were already translated - probably only not included in packages yet.
  9. The "configure event" is far from intuitive for bugzilla account configuration. The credentials should be explicitly requested from user if they are not configured instead of some strange error report.
  10. #191 When duplicate in Bugzilla is detected, abrt-gui should give more valuable information than "exit code = 139"
  11. there is no indications that something is being done during downloading debuginfo packages; some "loading..." message would prevent impatient user from closing the window untimely