Test Day:2012-10-01 ABRT: Difference between revisions

Revision as of 13:29, 1 October 2012

Fedora Test Days

[ABRT & libreport]

Date	2012-10-01
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?

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

Automated Bug Reporting Tool (ABRT)
Unified Problem Reporting UI (libreport)
Simplified crash reporting via ABRT Server (Fedora 18 Feature)
Gnome-abrt

Who's available

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

Development - Jiří Moskovčák (jmoskovc), Denys Vlasenko (dvlasenk), Karel Klíč (kklic), 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

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

How to test?

Update your machine

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

Live image

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

Download the nightly Fedora 18 build for your architecture. Choose the mainstream 'desktop' spin or any other desktop-like spin (kde, lxde, xfce).

Get latest abrt/libreport packages

The latest versions are:

abrt-2.0.13-1.fc18
libreport-2.0.14-1.fc18
btparser-0.19-1.fc18
gnome-abrt-0.2.2-1.fc18

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

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.

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

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.

New features or test cases

User	Simplified crash reporting	Reporting known crash	Ruby exceptions	Gnome ABRT	Configuration storage	References
Sample User	pass	warn ^[1]	fail ^[2]	inprogress	inprogress	↑ Test pass, but also encountered RHBZ #54321 ↑ RHBZ #12345
David Kutalek	inprogress	pass	inprogress	inprogress	inprogress
Michal Toman	pass	pass	warn ^[1]	pass	pass	↑ will-crash package is not built for F18, you need to install the F17 version from koji
Martin Kyral	warn ^[1]	pass	none	pass	pass	↑ Wrong BZ configuration leads to processing failure with no possibility of recovery RHBZ #861899
Iveta Senfeldova	pass ^[1]	pass	pass	pass	inprogress	↑ Problem with tabs highlighting, confusing warning message: https://bugzilla.redhat.com/show_bug.cgi?id=861880

Basic functionality

User	Basic test	Logger reporting	Bugzilla reporting	Mailx plugin	CLI interface	Kernel oops	Python crash	Kernel panic(vmcore)	References
David Kutalek	warn ^[1]	pass	pass	pass	pass	fail ^[2]	pass	inprogress	↑ Test passed, but processing window is wider then screen RHBZ #861872 ↑ Not able to report issue because of RHBZ #854266
Michal Toman	pass	pass	pass	pass	pass	fail ^[1]^[2]	pass	none	↑ AVC RHBZ #854266 ↑ In permissive doesn't work for the oops from the testcase, but works for all random oopses on my system.
Martin Kyral	pass	fail ^[1]	inprogress	inprogress	inprogress	inprogress	inprogress	inprogress	↑ Needed to repeat the procedure for the issue to be written in the log RHBZ #861973

Integration

User	sealert	anaconda	anaconda install	firstboot	Retrace cli	Retrace gui	References
David Kutalek	pass ^[1]	inprogress	inprogress	inprogress	inprogress	inprogress	↑ Tested appending to existing bug - works

[1] Test pass, but also encountered RHBZ #54321

[2] RHBZ #12345

[3] will-crash package is not built for F18, you need to install the F17 version from koji

[4] Wrong BZ configuration leads to processing failure with no possibility of recovery RHBZ #861899

[5] Problem with tabs highlighting, confusing warning message: https://bugzilla.redhat.com/show_bug.cgi?id=861880

[6] Test passed, but processing window is wider then screen RHBZ #861872

[7] Not able to report issue because of RHBZ #854266

[8] AVC RHBZ #854266

[9] In permissive doesn't work for the oops from the testcase, but works for all random oopses on my system.

[10] Needed to repeat the procedure for the issue to be written in the log RHBZ #861973

[11] Tested appending to existing bug - works

[1]

[2]

[1]

[1]

[1]

[1]

[2]

[1]

[2]

[1]

[1]

@@ Line 168: / Line 168: @@
 |-
 | [[User:mkyral|Martin Kyral]]
-| {{result|warn}} <ref>https://bugzilla.redhat.com/show_bug.cgi?id=861899</ref>
+| {{result|warn}} <ref>Wrong BZ configuration leads to processing failure with no possibility of recovery {{bz|861899}}</ref>
 | {{result|pass}}
 | {{result|none}}
@@ Line 222: / Line 222: @@
 | [[User:mtoman|Martin Kyral]]
 | {{result|pass}}
-| {{result|inprogress}}
+| {{result|fail}}  <ref>Needed to repeat the procedure for the issue to be written in the log {{bz|861973}}</ref>
 | {{result|inprogress}}
 | {{result|inprogress}}

Search

Test Day:2012-10-01 ABRT: Difference between revisions

Revision as of 13:29, 1 October 2012

Contents

What to test?

Who's available

Prerequisite for Test Day

How to test?

Update your machine

Live image

Get latest abrt/libreport packages

Test Cases

New features or test cases

Basic functionality

Integration

Test Results

New features or test cases

Basic functionality

Integration