Test Day:2013-05-07 ABRT: Difference between revisions

Latest revision as of 19:38, 26 June 2015

Fedora Test Days

[ABRT & libreport]

Date	2013-05-07
Time	6:00 UTC - 16:00 UTC

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

Today's instalment of Fedora Test Day will focus on:

Automated Bug Reporting Tool (ABRT)
Unified Problem Reporting UI (libreport)
Gnome-abrt
SEAlert integration
Tainted kernel links
abrt server UX

Who's available[edit]

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

Development - Jiří Moskovčák (jmoskovc), Denys Vlasenko (dvlasenk), Michal Toman (mtoman), Richard Marko (rmarko), Filák Jakub (jfilak), Lichvár Miroslav (mlichvar)
Quality Assurance - David Kutálek (dkutalek), Martin Kyral (mkyral)

Prerequisite for Test Day[edit]

Physical machine or a virtual machine
An updated Fedora 19 pre-release

How to test?[edit]

Update your machine[edit]

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

Live image[edit]

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

Architecture	SHA256SUM
x86_64 (version 3)	5b457aab4cdfdb42869eb5d500f8f96631286880afce158ef38397a13d16726e
i686 (version 3)	c044398025e7821cf59415753670de8cf9e1d27c720d87b1d369a9e47eb6f8cd

Get latest abrt/libreport packages[edit]

The latest versions are:

abrt-2.1.4-3.fc19
libreport-2.1.4-4.fc19
btparser-0.25-2.fc19
gnome-abrt-0.2.12-3.fc19

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 \
  btparser btparser-python \
  gnome-abrt elfutils

Elfutils needed
Please make sure you have elfutils installed - abrt-ccpp is missing requires - [Bug 859674]

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_pattern contains following output:

# cat /proc/sys/kernel/core_pattern
|/usr/libexec/abrt-hook-ccpp %s %c %p %u %g %t e

Test Cases[edit]

For better orientation there are several groups of test cases, top priority first. Follow each of these test cases, or just some group(s) of them in case of limited time for testing.

New and important features[edit]

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

Basic functionality[edit]

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

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.

Try to break Abrt
Besides above test cases, fell free to experiment and try to break Abrt in your own ways. We will be happy with that :-).

Test Results[edit]

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, or btparser for backtrace parser related bugs, or gnome-abrt for new Gnome Abrt GUI. 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.

Alternative reporting through the web application
If you are not familiar with the Wiki editing or you come here in prime time and there are a lot of conflicting edits in the Wiki, you can try to report your results via our web application. Results from this web application will be automatically transferred to the Wiki on 2013-05-21 and the alternative reporting system will be shut down to this date. Feel free to continue testing and filling the wiki even after this date. Please note the number of reports currently visible in the wiki doesn't correspond to the number of reports sent so far (i.e. reports sent through the web application).

F19 ABRT Testday application

Enable the testing repository
To have the freshest available abrt build, please enable the test-day abrt repository by downloading fedora-abrt.repo file and placing it in your /etc/yum.repos.d directory. This is important for the test day live image, as the image is missing some packages needed for some of the test cases and they are not present in the standard Fedora 19 repositories in the desired version. We aplologize for the inconvenience.

New and important features[edit]

User	Hardware	Reporting known crash	Ruby exceptions	Gnome ABRT	Configuration storage	SELinux alerts	Knowledgebase	ABRT server user experience	References
mkyral	VirtualBox	pass	pass	pass	pass	fail ^[1]	fail ^{[long 1]}		↑ The same issue as jkejda - clicking Report brings sealert window up, but having all the fields empty (ie. unable to report anything at all)
jmoskovc	kvm	pass}	pass	warn ^[1] pass ^{[long 2]}	pass	fail ^[2] fail ^{[long 3]}	pass	pass	↑ Killing gnome-abrt produces an empty core_backtrace, the basic functionality of gnome-abrt works ↑ AVC was visible in gnome-abrt, but setroubleshoot window was empty
lzachar	Lenovo T410	pass	pass	pass
isenfeld	Lenovo T420s	pass	pass		pass	warn ^[1]	pass		↑ Clicking on 'Report' didn't do anything for some reason. Should be tried again.
mhradile	Virtual Manager	pass	pass	fail ^[1] ^[2] ^[3]					↑ RHBZ #960640 ↑ RHBZ #960647 ↑ Also not all will_crashes were reported ;-) because it let me report this BZ#960625.
fholec	VirtualBox	pass
fholec	Lenovo IdeaPad S205	pass	pass	pass	pass		pass ^[1] pass		↑ VirtualBox downloaded different kernel as dependency -> not tested VLC -> OK Not able to install chrome, chromium, flash-plugin
jkejda	VirtualBox	pass	pass	pass	pass	fail ^[1]	pass	pass	↑ When you click on the 'Report' button SELinux Alert Browser start empty.

Basic functionality[edit]

User	Hardware	Basic test	Logger reporting	Bugzilla reporting	Mailx plugin	CLI interface	Kernel oops	Python crash	Kernel panic(vmcore)	Console notification	References
mkyral	VirtualBox	pass	pass						warn ^{[long 4]}	pass
jmoskovc	kvm	pass	pass ^[1]	pass	fail ^{[long 5]}	fail ^{[long 6]}	pass	pass	warn ^[2]	warn ^[3]	↑ It's not very easy to use the logger, the UI (cli nor gui) doesn't offer any convenient way for it ↑ didn't test ↑ Works, but prints errors on the first login: https://github.com/abrt/abrt/issues/649
mhradile	Virtual Manager						pass
fholec	Lenovo IdeaPad S205	pass	pass		pass ^[1]	warn ^[2]	pass	pass		pass	↑ Mail not received, but reported as sent ↑ Not able to remove directory of issue while logged in as liveuser
jkejda	VirtualBox	pass	pass	pass	warn ^{[long 7]}	fail warn ^{[long 8]}	pass	pass		pass

Long comments[edit]

↑ vlc crashes are taken as duplicate of the will_segfault crash. The bug is already known to the developers and is being fixed. After cleaning the crash directories the test PASSes
↑ The gnome-abrt itself works, but I hit a problem when trying to kill gnome-abrt: May 7 08:43:20 localhost abrtd: Directory 'ccpp-2013-05-07-08:43:19-1985' creation detected May 7 08:43:20 localhost abrt[2174]: Saved core dump of pid 1985 (/usr/bin/python2.7) to /var/tmp/abrt/ccpp-2013-05-07-08:43:19-1985 (37634048 bytes) May 7 08:43:20 localhost abrtd: BDB2053 Freeing read locks for locker 0x2b: 1920/139723609384960 May 7 08:43:20 localhost abrtd: BDB2053 Freeing read locks for locker 0x2c: 1920/139723609384960 May 7 08:43:20 localhost abrtd: BDB2053 Freeing read locks for locker 0x2d: 1920/139723609384960 May 7 08:43:20 localhost abrtd: BDB2053 Freeing read locks for locker 0x2e: 1920/139723609384960 May 7 08:43:20 localhost abrtd: Generating core_backtrace May 7 08:43:20 localhost abrtd: Generating backtrace May 7 08:43:23 localhost abrtd: Backtrace is generated, 17605 bytes May 7 08:43:24 localhost abrtd: Core backtrace is generated and saved, 0 bytes May 7 08:43:26 localhost abrtd: Duplicate: core backtrace May 7 08:43:26 localhost abrtd: DUP_OF_DIR: /var/tmp/abrt/ccpp-2013-05-07-07:50:47-1707 May 7 08:43:26 localhost abrtd: Deleting problem directory ccpp-2013-05-07-08:43:19-1985 (dup of ccpp-2013-05-07-07:50:47-1707)
↑ gnome-abrt shows the AVC correctly, but the setroubleshoot window (which appears after clicking the report button) is empty and there is no AVC
↑ crashkernel does not work at all (BZ#959914), tested notification only. notification was not shown, vmcore was listed in the problems after clicking 'All problems' and inserting root passwd.
↑ [liveuser@localhost ccpp-2013-05-07-10:08:18-2864]$ report-cli -e report_Mailx -- . Mailx Recipient: jmoskovc@redhat.com Mailx Sender: jmoskovc@redhat.com No changes were detected in the report Sending an email... /usr/sbin/sendmail: No such file or directory . . . message not sent. Error running '/bin/mailx' ('report_Mailx' exited with 1)
↑ [liveuser@localhost abrt]$ abrt-cli rm /var/tmp/abrt/ccpp-2013-05-07-10:08:18-2864 Can't remove directory '/var/tmp/abrt/ccpp-2013-05-07-10:08:18-2864': Permission denied [liveuser@localhost abrt]$ ls -l total 8 drwxrwx---. 2 liveuser abrt 40 May 7 10:57 ccpp-2013-05-07-10:08:18-2864
↑ Before testing: - install 'libreport-plugin-mailx' from http://repos.fedorapeople.org/repos/jfilak/abrt/fedora-abrt.repo - install 'sendmail' I still waiting for email =o/
↑ Reporting work (abrt-cli report to bugzilla) but not for Logger. This test case is wrong, command for report to Logger is 'report-cli -e report_Logger DIR'

[1] The same issue as jkejda - clicking Report brings sealert window up, but having all the fields empty (ie. unable to report anything at all)

[3] Killing gnome-abrt produces an empty core_backtrace, the basic functionality of gnome-abrt works

[5] AVC was visible in gnome-abrt, but setroubleshoot window was empty

[7] Clicking on 'Report' didn't do anything for some reason. Should be tried again.

[bz960640-8] RHBZ #960640

[bz960647-9] RHBZ #960647

[10] Also not all will_crashes were reported ;-) because it let me report this BZ#960625.

[11] VirtualBox downloaded different kernel as dependency -> not tested VLC -> OK Not able to install chrome, chromium, flash-plugin

[12] When you click on the 'Report' button SELinux Alert Browser start empty.

[14] It's not very easy to use the logger, the UI (cli nor gui) doesn't offer any convenient way for it

[17] 't test

[18] Works, but prints errors on the first login: https://github.com/abrt/abrt/issues/649

[19] Mail not received, but reported as sent

[20] Not able to remove directory of issue while logged in as liveuser

[2] vlc crashes are taken as duplicate of the will_segfault crash. The bug is already known to the developers and is being fixed. After cleaning the crash directories the test PASSes

[4] The gnome-abrt itself works, but I hit a problem when trying to kill gnome-abrt: May 7 08:43:20 localhost abrtd: Directory 'ccpp-2013-05-07-08:43:19-1985' creation detected May 7 08:43:20 localhost abrt[2174]: Saved core dump of pid 1985 (/usr/bin/python2.7) to /var/tmp/abrt/ccpp-2013-05-07-08:43:19-1985 (37634048 bytes) May 7 08:43:20 localhost abrtd: BDB2053 Freeing read locks for locker 0x2b: 1920/139723609384960 May 7 08:43:20 localhost abrtd: BDB2053 Freeing read locks for locker 0x2c: 1920/139723609384960 May 7 08:43:20 localhost abrtd: BDB2053 Freeing read locks for locker 0x2d: 1920/139723609384960 May 7 08:43:20 localhost abrtd: BDB2053 Freeing read locks for locker 0x2e: 1920/139723609384960 May 7 08:43:20 localhost abrtd: Generating core_backtrace May 7 08:43:20 localhost abrtd: Generating backtrace May 7 08:43:23 localhost abrtd: Backtrace is generated, 17605 bytes May 7 08:43:24 localhost abrtd: Core backtrace is generated and saved, 0 bytes May 7 08:43:26 localhost abrtd: Duplicate: core backtrace May 7 08:43:26 localhost abrtd: DUP_OF_DIR: /var/tmp/abrt/ccpp-2013-05-07-07:50:47-1707 May 7 08:43:26 localhost abrtd: Deleting problem directory ccpp-2013-05-07-08:43:19-1985 (dup of ccpp-2013-05-07-07:50:47-1707)

[6] -abrt shows the AVC correctly, but the setroubleshoot window (which appears after clicking the report button) is empty and there is no AVC

[13] rashkernel does not work at all (BZ#959914), tested notification only. notification was not shown, vmcore was listed in the problems after clicking 'All problems' and inserting root passwd.

[15] [liveuser@localhost ccpp-2013-05-07-10:08:18-2864]$ report-cli -e report_Mailx -- . Mailx Recipient: jmoskovc@redhat.com Mailx Sender: jmoskovc@redhat.com No changes were detected in the report Sending an email... /usr/sbin/sendmail: No such file or directory . . . message not sent. Error running '/bin/mailx' ('report_Mailx' exited with 1)

[16] [liveuser@localhost abrt]$ abrt-cli rm /var/tmp/abrt/ccpp-2013-05-07-10:08:18-2864 Can't remove directory '/var/tmp/abrt/ccpp-2013-05-07-10:08:18-2864': Permission denied [liveuser@localhost abrt]$ ls -l total 8 drwxrwx---. 2 liveuser abrt 40 May 7 10:57 ccpp-2013-05-07-10:08:18-2864

[21] Before testing: - install 'libreport-plugin-mailx' from http://repos.fedorapeople.org/repos/jfilak/abrt/fedora-abrt.repo - install 'sendmail' I still waiting for email =o/

[22] Reporting work (abrt-cli report to bugzilla) but not for Logger. This test case is wrong, command for report to Logger is 'report-cli -e report_Logger DIR'

[1]

[long 1]

[1]

[long 2]

[2]

[long 3]

[1]

[1]

[2]

[3]

[1]

[1]

[long 4]

[1]

[long 5]

[long 6]

[2]

[3]

[1]

[2]

[long 7]

[long 8]

@@ Line 159: / Line 159: @@
 | {{result|pass}}
 | {{result|fail}}  <ref>The same issue as jkejda - clicking Report brings sealert window up, but having all the fields empty (ie. unable to report anything at all)</ref>
-| {{result|fail}}  <ref>vlc crashes are taken as duplicate of the will_segfault crash. The bug is already known to the developers and is being fixed.
+| {{result|fail}}  <ref group="long">vlc crashes are taken as duplicate of the will_segfault crash. The bug is already known to the developers and is being fixed.
 After cleaning the crash directories the test PASSes</ref>
 |
@@ Line 168: / Line 168: @@
 | {{result|pass}
 | {{result|pass}}
-| {{result|warn}}  <ref>Killing gnome-abrt produces an empty core_backtrace, the basic functionality of gnome-abrt works</ref>{{result|pass}}  <ref>The gnome-abrt itself works, but I hit a problem when trying to kill gnome-abrt:
+| {{result|warn}}  <ref>Killing gnome-abrt produces an empty core_backtrace, the basic functionality of gnome-abrt works</ref>{{result|pass}}  <ref group="long">The gnome-abrt itself works, but I hit a problem when trying to kill gnome-abrt:
 May  7 08:43:20 localhost abrtd: Directory 'ccpp-2013-05-07-08:43:19-1985' creation detected
@@ Line 185: / Line 185: @@
 </ref>
 | {{result|pass}}
-| {{result|fail}}  <ref>AVC was visible in gnome-abrt, but setroubleshoot window was empty</ref>{{result|fail}}  <ref>gnome-abrt shows the AVC correctly, but the setroubleshoot window (which appears after clicking the report button) is empty and there is no AVC</ref>
+| {{result|fail}}  <ref>AVC was visible in gnome-abrt, but setroubleshoot window was empty</ref>{{result|fail}}  <ref group="long">gnome-abrt shows the AVC correctly, but the setroubleshoot window (which appears after clicking the report button) is empty and there is no AVC</ref>
 | {{result|pass}}
 | {{result|pass}}
@@ Line 286: / Line 286: @@
 |
 |
-| {{result|warn}}  <ref>crashkernel does not work at all (BZ#959914), tested notification only.
+| {{result|warn}}  <ref group="long">crashkernel does not work at all (BZ#959914), tested notification only.
 notification was not shown, vmcore was listed in the problems after clicking 'All problems' and inserting root passwd.</ref>
@@ Line 297: / Line 297: @@
 | {{result|pass}}  <ref>It's not very easy to use the logger, the UI (cli nor gui) doesn't offer any convenient way for it</ref>
 | {{result|pass}}
-| {{result|fail}}  <ref>[liveuser@localhost ccpp-2013-05-07-10:08:18-2864]$ report-cli -e report_Mailx -- .
+| {{result|fail}}  <ref group="long">[liveuser@localhost ccpp-2013-05-07-10:08:18-2864]$ report-cli -e report_Mailx -- .
 Mailx Recipient: jmoskovc@redhat.com
 Mailx Sender: jmoskovc@redhat.com
@@ Line 308: / Line 308: @@
 ('report_Mailx' exited with 1)
 </ref>
-| {{result|fail}}  <ref>[liveuser@localhost abrt]$ abrt-cli rm /var/tmp/abrt/ccpp-2013-05-07-10:08:18-2864
+| {{result|fail}}  <ref group="long">[liveuser@localhost abrt]$ abrt-cli rm /var/tmp/abrt/ccpp-2013-05-07-10:08:18-2864
 Can't remove directory '/var/tmp/abrt/ccpp-2013-05-07-10:08:18-2864': Permission denied
@@ Line 354: / Line 354: @@
 | {{result|pass}}
 | {{result|pass}}
-| {{result|warn}}  <ref>Before testing:
+| {{result|warn}}  <ref group="long">Before testing:
 - install 'libreport-plugin-mailx' from http://repos.fedorapeople.org/repos/jfilak/abrt/fedora-abrt.repo
 - install 'sendmail'
@@ Line 360: / Line 360: @@
 I still waiting for email =o/
 </ref>
-| {{result|fail}}  {{result|warn}}  <ref>Reporting work (abrt-cli report to bugzilla) but not for Logger. This test case is wrong, command for report to Logger is 'report-cli -e report_Logger DIR'</ref>
+| {{result|fail}}  {{result|warn}}  <ref group="long">Reporting work (abrt-cli report to bugzilla) but not for Logger. This test case is wrong, command for report to Logger is 'report-cli -e report_Logger DIR'</ref>
 | {{result|pass}}
 | {{result|pass}}
@@ Line 368: / Line 368: @@
 |}
-[[Category:Test Days]]  [[Category:Fedora 19 Test Days]]
+== Long comments ==
+<references group="long" />
+  [[Category:Fedora 19 Test Days]]

Search

Test Day:2013-05-07 ABRT: Difference between revisions

Latest revision as of 19:38, 26 June 2015

Contents

What to test?[edit]

Who's available[edit]

Prerequisite for Test Day[edit]

How to test?[edit]

Update your machine[edit]

Live image[edit]

Get latest abrt/libreport packages[edit]

Test Cases[edit]

New and important features[edit]

Basic functionality[edit]

Test Results[edit]

New and important features[edit]

Basic functionality[edit]

Long comments[edit]