From Fedora Project Wiki

(abrt 2 changes)
(use different test case from Git)
Line 4: Line 4:
 
# We will check that the {{command|abrt-dump-oops}} works and provides correct amount of crashes detected.
 
# We will check that the {{command|abrt-dump-oops}} works and provides correct amount of crashes detected.
 
# Download files:
 
# Download files:
#* [http://git.fedorahosted.org/git/?p=abrt.git;a=blob_plain;f=examples/cut_here.test;hb=HEAD cut_here.test]
+
#* [http://git.fedorahosted.org/git/?p=abrt.git;a=blob_plain;f=examples/oops1.test;h=e4f02d26c11cf613c522d577486ed9dfc597b1b7;hb=HEAD oops1.test]
 
#* [http://git.fedorahosted.org/git/?p=abrt.git;a=blob_plain;f=examples/not_oops3.test;hb=HEAD not_oops3.test]
 
#* [http://git.fedorahosted.org/git/?p=abrt.git;a=blob_plain;f=examples/not_oops3.test;hb=HEAD not_oops3.test]
 
# Test that stand-alone detector tool works properly; Do as a root for both files:
 
# Test that stand-alone detector tool works properly; Do as a root for both files:
#: $ abrt-dump-oops -d -o cut_here.test
+
#: $ abrt-dump-oops -d -o oops1.test
#: Version: 2.6.32-19.el6.x86_64
+
#: abrt-dump-oops: Found oopses: 1
#: WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:467
+
#:
#: generic_get_mtrr+0x11e/0x140() (Not tainted)
+
#: Version: 2.6.27.9-159.fc10.i686 #1
 +
#: BUG: unable to handle kernel NULL pointer dereference at 00000000
 
#: ...
 
#: ...
#: [<ffffffff810abcff>] sys_init_module+0xdf/0x250
+
#: EIP: [<f88dec25>] radeon_cp_init_ring_buffer+0x90/0x302 [radeon] SS:ESP 0068:f0a0cf08
#: [<ffffffff81013172>] system_call_fastpath+0x16/0x1b
 
 
#: abrt-dump-oops: Creating dump directories
 
#: abrt-dump-oops: Creating dump directories
 
# Open abrt-gui and look for the crash.
 
# Open abrt-gui and look for the crash.
 
# And now test if ABRT's scanning of /var/log/messages works, you'll need a root privs for this
 
# And now test if ABRT's scanning of /var/log/messages works, you'll need a root privs for this
 
# Make sure {{filename|/etc/abrt/abrt_event.conf}} contains <tt>EVENT=post-create analyzer=Kerneloops  abrt-action-analyze-oops</tt> and <tt>EVENT=report          analyzer=Kerneloops  abrt-action-kerneloops</tt>. If changed anything, restart abrtd:<tt> service abrtd restart</tt>.
 
# Make sure {{filename|/etc/abrt/abrt_event.conf}} contains <tt>EVENT=post-create analyzer=Kerneloops  abrt-action-analyze-oops</tt> and <tt>EVENT=report          analyzer=Kerneloops  abrt-action-kerneloops</tt>. If changed anything, restart abrtd:<tt> service abrtd restart</tt>.
# cat the downloaded file to {{filename|/var/log/messages}} e.g.:<pre>cat cut_here.test >> /var/log/messages</pre>
+
# cat the downloaded file to {{filename|/var/log/messages}} e.g.:<pre>cat oops1.test >> /var/log/messages</pre>
 
# If you are logged as a root: Wait for abrt-applet (make sure it's running) and notification to popup to show the notification about the detected kerneloops. Otherwise open abrt-gui as a root instead.
 
# If you are logged as a root: Wait for abrt-applet (make sure it's running) and notification to popup to show the notification about the detected kerneloops. Otherwise open abrt-gui as a root instead.
  
 
|results=
 
|results=
# After running {{command|abrt-dump-oops}} on {{filename|cut_here.test}} crash should be craeted nad visible via abrt-gui and in the terminal. Running the same command on {{filename|not_oops3.test}} should not create crash case.
+
# After running {{command|abrt-dump-oops}} on {{filename|oops1.test}} crash should be craeted and visible via abrt-gui and in the terminal. Running the same command on {{filename|not_oops3.test}} should not create crash case.
 
# After finishing the second part: oops was detected and is visible in abrt-gui.
 
# After finishing the second part: oops was detected and is visible in abrt-gui.
 
}}
 
}}
 
[[Category:Package_abrt_test_cases]]
 
[[Category:Package_abrt_test_cases]]

Revision as of 10:25, 15 March 2011

Description

This test case tests the functionality of the ABRT kerneloops feature.


How to test

  1. We will check that the abrt-dump-oops works and provides correct amount of crashes detected.
  2. Download files:
  3. Test that stand-alone detector tool works properly; Do as a root for both files:
    $ abrt-dump-oops -d -o oops1.test
    abrt-dump-oops: Found oopses: 1
    Version: 2.6.27.9-159.fc10.i686 #1
    BUG: unable to handle kernel NULL pointer dereference at 00000000
    ...
    EIP: [<f88dec25>] radeon_cp_init_ring_buffer+0x90/0x302 [radeon] SS:ESP 0068:f0a0cf08
    abrt-dump-oops: Creating dump directories
  4. Open abrt-gui and look for the crash.
  5. And now test if ABRT's scanning of /var/log/messages works, you'll need a root privs for this
  6. Make sure /etc/abrt/abrt_event.conf contains EVENT=post-create analyzer=Kerneloops abrt-action-analyze-oops and EVENT=report analyzer=Kerneloops abrt-action-kerneloops. If changed anything, restart abrtd: service abrtd restart.
  7. cat the downloaded file to /var/log/messages e.g.:
    cat oops1.test >> /var/log/messages
  8. If you are logged as a root: Wait for abrt-applet (make sure it's running) and notification to popup to show the notification about the detected kerneloops. Otherwise open abrt-gui as a root instead.

Expected Results

  1. After running abrt-dump-oops on oops1.test crash should be craeted and visible via abrt-gui and in the terminal. Running the same command on not_oops3.test should not create crash case.
  2. After finishing the second part: oops was detected and is visible in abrt-gui.