From Fedora Project Wiki
(rewrite (hope this is right, the original is shortened and unclear)) |
No edit summary |
||
| Line 8: | Line 8: | ||
#:ActionsAndReporters = RunApp("ls", "ls-output") | #:ActionsAndReporters = RunApp("ls", "ls-output") | ||
#:</pre> | #:</pre> | ||
{{admon/warning|The following test doesn't work|There is a regression in abrt that prevents this option to work.}} | |||
# Set up an executable-specific report action in the ''AnalyzerActionsAndReporters'' section, such as: | # Set up an executable-specific report action in the ''AnalyzerActionsAndReporters'' section, such as: | ||
#:<pre> | #:<pre> | ||
| Line 19: | Line 20: | ||
# Run the specified command (gedit in our example) and then kill it with the command {{command|kill -SIGSEGV (pid)}} | # Run the specified command (gedit in our example) and then kill it with the command {{command|kill -SIGSEGV (pid)}} | ||
|results= | |results= | ||
# Verify that a directory listing appears in the file {{filename|ls-output}} | # Verify that a directory listing appears in the file {{filename|ls-output}} located at /var/cache/abrt/<the_crash_directory> | ||
# Verify that the Mailx plugin was used to send a mail about the crash | #* the_crash_directory will be something like ccpp-1270110556-2295 (the format is: <analyzer>-<time>-<pid>) | ||
# -- DOESN'T WORK --Verify that the Mailx plugin was used to send a mail about the crash | |||
}} | }} | ||
[[Category:ABRT_Test_Cases]] | [[Category:ABRT_Test_Cases]] | ||
Revision as of 08:40, 1 April 2010
Description
This test case checks whether ABRT's actions and reporters function works correctly.
How to test
- Ensure the appropriate packages are installed with the command
su -c 'yum install abrt-plugin-runapp abrt-plugin-mailx' - Edit the config file
/etc/abrt/abrt.conf, and change the ActionsAndReporters line to read:- ActionsAndReporters = RunApp("ls", "ls-output")
The following test doesn't work
There is a regression in abrt that prevents this option to work.
There is a regression in abrt that prevents this option to work.
- Set up an executable-specific report action in the AnalyzerActionsAndReporters section, such as:
- [ AnalyzerActionsAndReporters ]
- # all C/C++ crashes will be reported via Logger plugin
- CCpp = Logger
- # if gedit crashes, then an email will be send and Logger (from ''CCpp'' section) should be silent
- CCpp:gedit = Mailx("[abrt] Gedit crashed")
- Restart ABRT with the command
su -c 'service abrtd restart' - Run the specified command (gedit in our example) and then kill it with the command
kill -SIGSEGV (pid)
Expected Results
- Verify that a directory listing appears in the file
ls-outputlocated at /var/cache/abrt/<the_crash_directory>- the_crash_directory will be something like ccpp-1270110556-2295 (the format is: <analyzer>-
- -- DOESN'T WORK --Verify that the Mailx plugin was used to send a mail about the crash