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/ | #* [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 | #: $ abrt-dump-oops -d -o oops1.test | ||
#: Version: 2.6. | #: 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 | #: 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 | # 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| | # 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
- We will check that the
abrt-dump-oopsworks and provides correct amount of crashes detected. - Download files:
- 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
- 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
- Make sure
/etc/abrt/abrt_event.confcontains 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. - cat the downloaded file to
/var/log/messagese.g.:cat oops1.test >> /var/log/messages
- 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
- After running
abrt-dump-oopsonoops1.testcrash should be craeted and visible via abrt-gui and in the terminal. Running the same command onnot_oops3.testshould not create crash case. - After finishing the second part: oops was detected and is visible in abrt-gui.