From Fedora Project Wiki

m (moved QA:TestCase ABRT BlackList to QA:Testcase ABRT BlackList: Renamed with proper QA:Testcase prefix)
(update path to the configuration file)
 
Line 2: Line 2:
 
|description=This test case checks whether ABRT blacklisting of certain packages works correctly.
 
|description=This test case checks whether ABRT blacklisting of certain packages works correctly.
 
|actions=
 
|actions=
# Edit the config file {{filename|/etc/abrt/abrt.conf}} and find the lines:  
+
# Edit the config file {{filename|/etc/abrt/abrt-action-save-package-data.conf}} and find the lines:  
 
#: # Blacklisted packages
 
#: # Blacklisted packages
 
#: BlackList = nspluginwrapper,valgrind,strace,avant-window-navigator
 
#: BlackList = nspluginwrapper,valgrind,strace,avant-window-navigator

Latest revision as of 08:28, 31 October 2013

Description

This test case checks whether ABRT blacklisting of certain packages works correctly.


How to test

  1. Edit the config file /etc/abrt/abrt-action-save-package-data.conf and find the lines:
    # Blacklisted packages
    BlackList = nspluginwrapper,valgrind,strace,avant-window-navigator
  2. Add a package whose application you can conveniently crash to the list or crash one from the current list
  3. Restart abrt with the command su -c 'systemctl restart abrtd.service'
  4. Run one of the blacklisted commands - e.g. run strace sleep 3m - and then kill the application from the newly blacklisted package with the command kill -SIGSEGV $(strace_pid)

Expected Results

  1. ABRT should ignore the crash of the blacklisted application
  2. Look to /var/log/messages for 'abrt[6443]: saved core dump of pid 6428 (/usr/bin/strace)' and 'Corrupted or bad dump /var/spool/abrt/ccpp-... (res:2), deleting'