From Fedora Project Wiki

Line 19: Line 19:
 
oops1.test and oops3.test should contain one and three oopses respectively. not_oopsN.test should not be detected as containing oops.
 
oops1.test and oops3.test should contain one and three oopses respectively. not_oopsN.test should not be detected as containing oops.
 
# Optional. Edit /etc/abrt/abrt.conf so it says: <pre>10 = KerneloopsScanner</pre> This makes abrtd scan /var/log/messages more often, every 10 secs. Then restart abrtd:<pre>$ service abrtd restart</pre>
 
# Optional. Edit /etc/abrt/abrt.conf so it says: <pre>10 = KerneloopsScanner</pre> This makes abrtd scan /var/log/messages more often, every 10 secs. Then restart abrtd:<pre>$ service abrtd restart</pre>
# cat the downloaded file to /var/log/messages e.g.:<pre>cat oops1.test /var/log/messages</pre>
+
# cat the downloaded file to /var/log/messages e.g.:<pre>cat oops1.test >> /var/log/messages</pre>
 
#* you'll need root privs for this
 
#* you'll need root privs for this
 
# Wait for abrt-applet (make sure it's running) to show the notification about the detected kerneloops
 
# Wait for abrt-applet (make sure it's running) to show the notification about the detected kerneloops

Revision as of 09:01, 1 April 2010

Description

This test case tests the functionality of the ABRT feature.


How to test

  1. We will check that the KerneloopsScanner, works and provides correct amount of crashes detected.
  2. Download files:
  3. Test that stand-alone detector tool is working properly:
$ dumpoops -s oops1.test
dumpoops: found oopses: 1
Version: 2.6.27.9-159.fc10.i686 #1
BUG: unable to handle kernel NULL pointer dereference at 00000000
...

oops1.test and oops3.test should contain one and three oopses respectively. not_oopsN.test should not be detected as containing oops.

  1. Optional. Edit /etc/abrt/abrt.conf so it says:
    10 = KerneloopsScanner
    This makes abrtd scan /var/log/messages more often, every 10 secs. Then restart abrtd:
    $ service abrtd restart
  2. cat the downloaded file to /var/log/messages e.g.:
    cat oops1.test >> /var/log/messages
    • you'll need root privs for this
  3. Wait for abrt-applet (make sure it's running) to show the notification about the detected kerneloops
  4. Open the abrt-gui and check if you can see the oops

Expected Results

  1. Oopses detected and visible in abrt-gui