From Fedora Project Wiki
(Drop direct Test Days category membership)
 
(21 intermediate revisions by 9 users not shown)
Line 20: Line 20:
* '''Automated Bug Reporting Tool ([https://fedorahosted.org/abrt ABRT])'''  
* '''Automated Bug Reporting Tool ([https://fedorahosted.org/abrt ABRT])'''  
* '''Unified Problem Reporting UI ([[Features/Unified Problem Reporting UI|libreport]])'''
* '''Unified Problem Reporting UI ([[Features/Unified Problem Reporting UI|libreport]])'''
* '''Simplified crash reporting via ABRT Server ([[Features/SimplifiedCrashReporting|Fedora 18 Feature]])'''
* '''Gnome-abrt'''
* '''Gnome-abrt'''
* '''SEAlert integration'''
* '''SEAlert integration'''
Line 50: Line 49:
! Architecture !! SHA256SUM  
! Architecture !! SHA256SUM  
|-  
|-  
| [http://fedorapeople.org/groups/qa/testday-20130507-x86_64.iso x86_64] || 6277f319b43b05df164eed859554865e1f7304ca66004cd2bdd6ce962b9ce7d9
| [http://fedorapeople.org/groups/qa/testday-20130507-3-x86_64.iso x86_64] (version 3) || 5b457aab4cdfdb42869eb5d500f8f96631286880afce158ef38397a13d16726e
|-
|-
| [http://fedorapeople.org/groups/qa/testday-20130507-i686.iso i686] || 25b0be65f391c941a36f3941bbde024836dee6161061487ceb7b39ad84974a58
| [http://fedorapeople.org/groups/qa/testday-20130507-3-i686.iso i686] (version 3) || c044398025e7821cf59415753670de8cf9e1d27c720d87b1d369a9e47eb6f8cd
|}
|}


Line 59: Line 58:
The latest versions are:
The latest versions are:


abrt-2.1.4-1.fc19<br/>
abrt-2.1.4-3.fc19<br/>
libreport-2.2.4-1.fc19<br/>
libreport-2.1.4-4.fc19<br/>
btparser-0.19-1.fc19<br>
btparser-0.25-2.fc19<br>
gnome-abrt-0.2.12-1.fc19
gnome-abrt-0.2.12-3.fc19


Use the following command to install/update all of them:
Use the following command to install/update all of them:
Line 98: Line 97:


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


=== New and important features ===
=== New and important features ===


# [[Features/SimplifiedCrashReporting]] - Simplified Crash Reporting (F18 Feature)
# [[QA:Testcase ABRT Reporting Known Crash]] - reporting of known crash
# [[QA:Testcase ABRT Reporting Known Crash]] - reporting of known crash
# [[QA:Testcase ABRT ruby gem]] - ruby exceptions
# [[QA:Testcase ABRT ruby gem]] - ruby exceptions
Line 121: Line 119:
# [[QA:Testcase ABRT python]] - python tracebacks
# [[QA:Testcase ABRT python]] - python tracebacks
# [[QA:Testcase ABRT vmcore]] - kernel oops
# [[QA:Testcase ABRT vmcore]] - kernel oops
 
# [[QA:Testcase ABRT cnotify]] - console notification
=== Integration ===
 
# [[QA:Testcase Libreport sealert]] - sealert integration
# [[QA:Testcase Libreport anaconda]] - anaconda integration
# [[QA:Testcase Libreport Anaconda Install]] - anaconda integration (directly in install)
# [[QA:Testcase Retrace Server CLI]] - Retrace Server CLI
# [[QA:Testcase Retrace Server GUI]] - Retrace Server in ABRT GUI


{{admon/important|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.}}
{{admon/important|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.}}
Line 142: Line 133:
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=abrt abrt], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=libreport libreport] for bugs in the libreport library, or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=btparser btparser] for backtrace parser related bugs, or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=gnome-abrt 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 [[Template:result|result template]] to enter your result, as shown in the example result line.
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=abrt abrt], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=libreport libreport] for bugs in the libreport library, or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=btparser btparser] for backtrace parser related bugs, or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=gnome-abrt 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 [[Template:result|result template]] to enter your result, as shown in the example result line.


{{admon/important|Important workaround|As of now, abrt contains a bug which prevents it from working properly after booting from LiveCD. If you booted from the live image, please do ''systemctl restart abrtd'' as root before starting.}}
{{admon/note|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).}}
[http://autoqa-stg.fedoraproject.org/testdays/show_event?event_id=4 F19 ABRT Testday application]
 
{{admon/important|Enable the testing repository|To have the freshest available abrt build, please enable the test-day abrt repository by downloading [http://repos.fedorapeople.org/repos/jfilak/abrt/fedora-abrt.repo 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 ====
==== New and important features ====
Line 148: Line 142:
{|
{|
! User
! User
! [[QA:Testcase_ABRT|Simplified crash reporting]]
! Hardware
! [[QA:Testcase_ABRT_Logger|Reporting known crash]]
! [[QA:Testcase_ABRT_Reporting_Known_Crash|Reporting known crash]]
! [[QA:Testcase ABRT ruby gem|Ruby exceptions]]
! [[QA:Testcase ABRT ruby gem|Ruby exceptions]]
! [[QA:Testcase GNOME ABRT MAIN|Gnome ABRT]]
! [[QA:Testcase GNOME ABRT MAIN|Gnome ABRT]]
! [[QA:Testcase_ABRT_Configuration_Storage|Configuration storage]]
! [[QA:Testcase_ABRT_Configuration_Storage|Configuration storage]]
! [[QA:Testcase_ABRT_SELinux|SELinux alerts]]
! [[QA:Testcase_ABRT_SELinux|SELinux alerts]]
! [[QA:Testcase_ABRT_tainted|Knowledgebase]]
! [[QA:Testcase ABRT Knowledgebase|Knowledgebase]]
! [[QA:Testcase_ABRT_Srv_UX|ABRT server user experience]]
! [[QA:Testcase_ABRT_server|ABRT server user experience]]
! References
! References
|-
|-
| [[User:SampleUser|Sample User]]
| [[User:mkyral|mkyral]]
| VirtualBox
| {{result|pass}} 
| {{result|pass}} 
| {{result|pass}} 
| {{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 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>
|
| <references/>
|-
| [[User:jmoskovc|jmoskovc]]
| kvm
| {{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 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
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)
</ref>
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</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|fail}} <ref>{{bz|12345}}</ref>
| {{result|pass}} 
| {{result|inprogress}}
| {{result|pass}} 
| {{result|inprogress}}
| <references/>
| {{result|inprogress}}
|-
| {{result|inprogress}}
| [[User:lzachar|lzachar]]
| {{result|inprogress}}
| Lenovo T410
| {{result|pass}}
| {{result|pass}} 
| {{result|pass}} 
|
|
|
|
| <references/>
|-
| [[User:isenfeld|isenfeld]]
| Lenovo T420s
| {{result|pass}} 
| {{result|pass}} 
|
| {{result|pass}} 
| {{result|warn}}  <ref>Clicking on 'Report' didn't do anything for some reason. Should be tried again.</ref>
| {{result|pass}} 
|
| <references/>
|-
| [[User:mhradile|mhradile]]
| Virtual Manager
| {{result|pass}} 
| {{result|pass}} 
| {{result|fail||960640|960647}}<ref>Also not all will_crashes were reported ;-) because it let me report this BZ#960625.</ref>
|
|
|
|
| <references/>
|-
| [[User:fholec|fholec]]
| VirtualBox
| {{result|pass}} 
|
|
|
|
|
|
| <references/>
|-
| [[User:fholec|fholec]]
| Lenovo IdeaPad S205
| {{result|pass}} 
| {{result|pass}} 
| {{result|pass}} 
| {{result|pass}}
|
| {{result|pass}}  <ref>VirtualBox downloaded different kernel as dependency -> not tested
 
VLC -> OK
 
Not able to install chrome, chromium, flash-plugin</ref>{{result|pass}} 
|
| <references/>
|-
| [[User:jkejda|jkejda]]
| VirtualBox
| {{result|pass}} 
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}  
| {{result|fail}} <ref>When you click on the 'Report' button SELinux Alert Browser start empty.</ref>
| {{result|pass}} 
| {{result|pass}}
| <references/>
| <references/>
|}
|}
Line 174: Line 265:
{|
{|
! User
! User
! Hardware
! [[QA:Testcase_ABRT|Basic test]]
! [[QA:Testcase_ABRT|Basic test]]
! [[QA:Testcase_ABRT_Logger|Logger reporting]]
! [[QA:Testcase_ABRT_Logger|Logger reporting]]
Line 182: Line 274:
! [[QA:Testcase ABRT python|Python crash]]
! [[QA:Testcase ABRT python|Python crash]]
! [[QA:Testcase ABRT vmcore|Kernel panic(vmcore)]]
! [[QA:Testcase ABRT vmcore|Kernel panic(vmcore)]]
! [[QA:Testcase_ABRT_cnotify|Console notification]]
! References
! References
|-
|-
| [[User:SampleUser|Sample User]]
| [[User:mkyral|mkyral]]
| {{result|pass}}
| VirtualBox
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| {{result|pass}}
| {{result|fail}} <ref>{{bz|12345}}</ref>
| {{result|pass}}
| {{result|inprogress}}
|  
| {{result|inprogress}}
|  
| {{result|inprogress}}
|  
| {{result|inprogress}}
|  
| {{result|inprogress}}
|  
| {{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>
| {{result|pass}}
| <references/>
| <references/>
|}
|-
| [[User:jmoskovc|jmoskovc]]
| kvm
| {{result|pass}} 
| {{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 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
 
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)
</ref>
| {{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


==== Integration ====
[liveuser@localhost abrt]$ ls -l
total 8
drwxrwx---. 2 liveuser abrt  40 May  7 10:57 ccpp-2013-05-07-10:08:18-2864
</ref>
| {{result|pass}} 
| {{result|pass}} 
| {{result|warn}}  <ref>didn't test</ref>
| {{result|warn}}  <ref>Works, but prints errors on the first login:


{|
https://github.com/abrt/abrt/issues/649</ref>
! User
| <references/>
! [[QA:Testcase Libreport sealert|sealert]]
|-
! [[QA:Testcase Libreport anaconda|anaconda]]
| [[User:mhradile|mhradile]]
! [[QA:Testcase Libreport Anaconda Install|anaconda install]]
| Virtual Manager
! [[QA:Testcase Libreport firstboot|firstboot]]
|
! [[QA:Testcase Retrace Server CLI|Retrace cli]]
|
! [[QA:Testcase Retrace Server GUI|Retrace gui]]
|
! References
|
|
| {{result|pass}} 
|
|
|
| <references/>
|-
| [[User:fholec|fholec]]
| Lenovo IdeaPad S205
| {{result|pass}} 
| {{result|pass}} 
|
| {{result|pass}}  <ref>Mail not received, but reported as sent</ref>
| {{result|warn}}  <ref>Not able to remove directory of issue while logged in as liveuser</ref>
| {{result|pass}} 
| {{result|pass}} 
|  
| {{result|pass}} 
| <references/>
|-
|-
| [[User:SampleUser|Sample User]]
| [[User:jkejda|jkejda]]
| {{result|pass}}
| VirtualBox
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| {{result|pass}}
| {{result|fail}} <ref>{{bz|12345}}</ref>
| {{result|pass}}
| {{result|inprogress}}
| {{result|pass}} 
| {{result|inprogress}}
| {{result|warn}} <ref group="long">Before testing:
| {{result|inprogress}}
- install 'libreport-plugin-mailx' from http://repos.fedorapeople.org/repos/jfilak/abrt/fedora-abrt.repo
- install 'sendmail'
 
I still waiting for email =o/
</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}}
|
| {{result|pass}}
| <references/>
| <references/>
|}
|}


[[Category:Test Days]]
== Long comments ==
<references group="long" />
 
  [[Category:Fedora 19 Test Days]]

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]

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]

  1. QA:Testcase ABRT Reporting Known Crash - reporting of known crash
  2. QA:Testcase ABRT ruby gem - ruby exceptions
  3. QA:Testcase GNOME ABRT MAIN - gnome-abrt
  4. QA:Testcase ABRT Configuration Storage - configuration storage
  5. QA:Testcase ABRT SELinux - ABRT GUI now catches AVC messages, too
  6. QA:Testcase ABRT Knowledgebase - ABRT provides more information about common problems
  7. QA:Testcase ABRT server - ABRT server user experience

Basic functionality[edit]

  1. QA:Testcase_ABRT - Basic test
  2. QA:Testcase_ABRT_Logger - Logger plugin
  3. QA:Testcase_ABRT_Bugzilla - Bugzilla plugin
  4. QA:Testcase_ABRT_Mailx - Mailx plugin
  5. QA:Testcase ABRT CLI - CLI interface
  6. QA:Testcase ABRT kernel - kernel oops
  7. QA:Testcase ABRT python - python tracebacks
  8. QA:Testcase ABRT vmcore - kernel oops
  9. 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
Pass pass
Pass pass
Fail fail
[1]
Fail fail
[long 1]
  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 pass
Warning warn
[1]
Pass pass
[long 2]
Pass pass
Fail fail
[2]
Fail fail
[long 3]
Pass pass
Pass pass
  1. ↑ Killing gnome-abrt produces an empty core_backtrace, the basic functionality of gnome-abrt works
  2. ↑ AVC was visible in gnome-abrt, but setroubleshoot window was empty
lzachar Lenovo T410
Pass pass
Pass pass
Pass pass
isenfeld Lenovo T420s
Pass pass
Pass pass
Pass pass
Warning warn
[1]
Pass pass
  1. ↑ Clicking on 'Report' didn't do anything for some reason. Should be tried again.
mhradile Virtual Manager
Pass pass
Pass pass
Fail fail [1] [2]
[3]
  1. ↑ RHBZ #960640
  2. ↑ RHBZ #960647
  3. ↑ Also not all will_crashes were reported ;-) because it let me report this BZ#960625.
fholec VirtualBox
Pass pass
fholec Lenovo IdeaPad S205
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
[1]
Pass pass
  1. ↑ VirtualBox downloaded different kernel as dependency -> not tested VLC -> OK Not able to install chrome, chromium, flash-plugin
jkejda VirtualBox
Pass pass
Pass pass
Pass pass
Pass pass
Fail fail
[1]
Pass pass
Pass pass
  1. ↑ 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
Pass pass
Warning warn
[long 4]
Pass pass
jmoskovc kvm
Pass pass
Pass pass
[1]
Pass pass
Fail fail
[long 5]
Fail fail
[long 6]
Pass pass
Pass pass
Warning warn
[2]
Warning warn
[3]
  1. ↑ It's not very easy to use the logger, the UI (cli nor gui) doesn't offer any convenient way for it
  2. ↑ didn't test
  3. ↑ Works, but prints errors on the first login: https://github.com/abrt/abrt/issues/649
mhradile Virtual Manager
Pass pass
fholec Lenovo IdeaPad S205
Pass pass
Pass pass
Pass pass
[1]
Warning warn
[2]
Pass pass
Pass pass
Pass pass
  1. ↑ Mail not received, but reported as sent
  2. ↑ Not able to remove directory of issue while logged in as liveuser
jkejda VirtualBox
Pass pass
Pass pass
Pass pass
Warning warn
[long 7]
Fail fail
Warning warn
[long 8]
Pass pass
Pass pass
Pass pass

Long comments[edit]

  1. ↑ 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
  2. ↑ 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)
  3. ↑ gnome-abrt shows the AVC correctly, but the setroubleshoot window (which appears after clicking the report button) is empty and there is no AVC
  4. ↑ 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.
  5. ↑ [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)
  6. ↑ [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
  7. ↑ 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/
  8. ↑ 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'
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:2013-05-07_ABRT&oldid=416650"