From Fedora Project Wiki

(clean up)
Line 8: Line 8:
 
#:        nice sosreport --tmp-dir "$DUMP_DIR" --batch \
 
#:        nice sosreport --tmp-dir "$DUMP_DIR" --batch \
 
#: [...]
 
#: [...]
# Restart abrtd service {{command|su -c 'service abrtd restart'}}
+
# Restart the abrtd service: {{command|su -c 'systemctl restart abrtd.service'}}
# Kill some app (this time it might take some time (~20 s) before the icon appears, as it waits for sosreport to finish)
+
# Crash a running application, with the command {{command|pkill -SIGSEGV (appname)}}
|results=
+
# Wait for a crash notification to appear: it might take some time (~20 s) before the icon appears, as it waits for sosreport to finish
 +
|results
 
# Verify that the file {{filename|sosreport.tar.xz}} exists in directory {{filename|/var/cache/abrt/<the_crash_directory>}} and has some reasonable content  
 
# Verify that the file {{filename|sosreport.tar.xz}} exists in directory {{filename|/var/cache/abrt/<the_crash_directory>}} and has some reasonable content  
# The tarball should contain config files from /etc, grub.conf, some info from /proc, loaded modules, and much more.
+
# The tarball should contain config files from /etc, grub.conf, some info from /proc, loaded modules, and much more
 
}}
 
}}
 
[[Category:Package_abrt_test_cases]]
 
[[Category:Package_abrt_test_cases]]

Revision as of 18:07, 29 March 2011

Description

This test case checks whether sosreport cooperates with ABRT correctly.


How to test

  1. Ensure the Package-x-generic-16.pngsos package is installed with the command su -c 'yum install sos'
  2. Edit the config file /etc/abrt/abrt_event.conf, and comment out lines
    #EVENT=post-create
    nice sosreport --tmp-dir "$DUMP_DIR" --batch \
    [...]
  3. Restart the abrtd service: su -c 'systemctl restart abrtd.service'
  4. Crash a running application, with the command pkill -SIGSEGV (appname)
  5. Wait for a crash notification to appear: it might take some time (~20 s) before the icon appears, as it waits for sosreport to finish

Expected Results

  1. Step #1 completes without error
  2. The system boots into runlevel 5
  3. Program completes with exit code 0