|
|
Line 143: |
Line 143: |
| | {{result|pass}} | | | {{result|pass}} |
| | {{result|pass}} <ref>Event settings for kernel opps is located in /etc/abrt/events.d/koops_events.conf</ref> <ref>abrt-dump-opps log scanner has parameters -drwx (not -drw)</ref> | | | {{result|pass}} <ref>Event settings for kernel opps is located in /etc/abrt/events.d/koops_events.conf</ref> <ref>abrt-dump-opps log scanner has parameters -drwx (not -drw)</ref> |
| | {{result|inprogress}} | | | {{result|warn}} <ref>[https://bugzilla.redhat.com/show_bug.cgi?id=692465#c5]</ref> |
| | {{result|inprogress}} | | | {{result|inprogress}} |
| | {{result|inprogress}} | | | {{result|inprogress}} |
Revision as of 14:11, 31 March 2011
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 bootThere 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:
- QA:Testcase ABRT CCPP addon - C/C++ tracebacks
- QA:Testcase ABRT python - python tracebacks
- QA:Testcase ABRT kernel - kernel oops
- QA:TestCase ABRT BlackList - package blacklist
- QA:Testcase ABRT quota - limiting the space occupied by ABRT's cache
- QA:Testcase ABRT Bugzilla - Bugzilla plugin
- QA:Testcase ABRT Logger - Logger plugin
- QA:Testcase ABRT Mailx - Mailx plugin
- QA:Testcase ABRT SOSreport plugin - sosreport integration with ABRT
- QA:Testcase ABRT GUI MAIN - testing the GUI (probably already during the previous steps, so just to sum it up)
- QA:Testcase ABRT CLI - CLI interface
- QA:Testcase ABRT GUI Localized - exploring localized GUI
- QA:Testcase ABRT CLI Localized - exploring localized CLI
- QA:Testcase Retrace Server CLI - Retrace Server CLI
- QA:Testcase Retrace Server GUI - Retrace Server in ABRT GUI
- 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
|
warn [1]
|
fail [2]
|
none
|
none
|
none
|
pass
|
pass
|
none
|
none
|
none
|
pass
|
pass
|
none
|
none
|
none
|
|
Jaroslav Škarvada
|
warn [1]
[2]
[3]
[4]
|
pass
|
warn [5]
|
fail
|
pass
|
pass [6]
|
pass
|
pass [7]
|
pass
|
warn [8]
|
pass [9]
[10]
|
fail [11]
|
fail [12]
|
pass [13]
|
pass
|
pass
|
- ↑ 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
- ↑ 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'.
- ↑ There is no "Open ABRT" button, only "Show".
- ↑ Got message: Missing separate debuginfo for
Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/45/190d029703ca464ad5c5eb6b7f99426a51a2e3
- ↑ There was no notification after the /var/log/messages modification.
- ↑ 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.
- ↑ 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.
- ↑ There is no "Edit->Plugins", probably "Edit->Event configuration" was meant and it worked as expected.
- ↑ 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.
- ↑ In this test case several instructions are misplaced to "Expected results".
- ↑ 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.
- ↑ A lot of messages are not localized to cs_CZ, e.g. "is not writable", "Choose option", "Analyzing coredump" and much much more.
- ↑ It is not clear from the testcase where "batch" command stores downloaded data.
|
David Kutalek
|
warn [1] [2]
|
pass
|
pass [3] [4]
|
warn [5]
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
- ↑ RHBZ #692428 - Report button in warning inside KDE info area does not work
- ↑ RHBZ #692433 - Cannot connect to Gnome keyring daemon dialog becomes annoying
- ↑ Event settings for kernel opps is located in /etc/abrt/events.d/koops_events.conf
- ↑ abrt-dump-opps log scanner has parameters -drwx (not -drw)
- ↑ [1]
|
Vít Ondruch
|
warn [1]
[2]
[3]
|
pass
|
warn
[4]
[5]
|
fail
[6]
|
warn
[7]
|
pass
[8]
|
pass
|
|
fail
[9]
|
warn
[10]
|
|
|
|
|
|
|
- ↑ Same experience as jskarvad
- ↑ RHBZ #692442 - Hi res image for "bug-reporting-window" and task switcher
- ↑ RHBZ #692444 - "bug-reporting-window" should be shown as "part of the application"
- ↑ abrt_event.conf does not contain the events mentioned in test case
- ↑ abrt.conf contains -drwx instead of -drw
- ↑ RHBZ #692465 - Blacklist doesn't work
- ↑ RHBZ #692474 - Exceeded quota is not reported
- ↑ 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.
- ↑ I have not /var/cache/abrt directory on my system. Even if I create one, nothing appears in there.
- ↑ RHBZ #692516 - The ABRT icon is almost invisible in panel
|
kparal
|
pass
|
fail [1]
|
none
|
none
|
none
|
none
|
none
|
none
|
none
|
none
|
none
|
none
|
none
|
none
|
none
|
none
|
- ↑ "abrtd: New dump directory /var/spool/abrt/pyhook-..., processing" in messages, but nothing happens.
|
Michal Nowak
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
|