From Fedora Project Wiki
(kill -USR2 seems to be more reliable than -USR1) |
(after looking into the source code and discussing with vpodzime, USR1 is the correct signal to trigger. USR2 creates an info dump, similar to USR1, but no fake crash and no libreport window) |
||
| Line 6: | Line 6: | ||
|actions= | |actions= | ||
# Boot the installer by any available means. | # Boot the installer by any available means. | ||
# If you know how to make Anaconda crash, you can do so. Otherwise use Anaconda's [http://lists.fedoraproject.org/pipermail/test/2012-September/110149.html fake exception handling trigger] - run the following command: <pre>kill - | # If you know how to make Anaconda crash, you can do so. Otherwise use Anaconda's [http://lists.fedoraproject.org/pipermail/test/2012-September/110149.html fake exception handling trigger] - run the following command: <pre>kill -USR1 `cat /var/run/anaconda.pid`</pre> Switch back to the GUI, an error dialog should be displayed after a few seconds (sometimes you might need to click on some UI element to achieve that). | ||
# Check that a file with all the crash details has been created in {{filename|/tmp/anaconda-tb-*}}. | # Check that a file with all the crash details has been created in {{filename|/tmp/anaconda-tb-*}}. | ||
# Report the exception to Bugzilla using the error dialog. | # Report the exception to Bugzilla using the error dialog. | ||
Revision as of 12:45, 18 September 2014
Associated release criterion
This test case is associated with the Basic_Release_Criteria#failure-reporting release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
This test case is associated with the Basic_Release_Criteria#failure-reporting release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
Description
This test case is intended to introduce a failure, and validate anaconda is able to properly handle the failure and report the issue to bugzilla. A valid bugzilla username and password is required for this test, please refer to BugsAndFeatureRequests.
Setup
Download, or create, boot media needed to boot and test the Fedora installer
How to test
- Boot the installer by any available means.
- If you know how to make Anaconda crash, you can do so. Otherwise use Anaconda's fake exception handling trigger - run the following command:
kill -USR1 `cat /var/run/anaconda.pid`
Switch back to the GUI, an error dialog should be displayed after a few seconds (sometimes you might need to click on some UI element to achieve that). - Check that a file with all the crash details has been created in
/tmp/anaconda-tb-*. - Report the exception to Bugzilla using the error dialog.
- If you used the fake exception handling trigger, go to Bugzilla and close the newly reported bug as NOTABUG.
Expected Results
- The installer presents a failure dialog and allows you to report it to Bugzilla.
- Exception traceback is displayed.
- Crash details are saved into
/tmp/anaconda-tb-*. - After reporting to Bugzilla, depending on the traceback you are either informed that a new bug was created, or that an existing bug was found that matches this failure. Either way, a bug number is provided.
- Details of the failure are attached to the bug report.