| Fedora Test Days | |
|---|---|
| |
| Kdump Test Day | |
| Date | 27 March 2012 |
| Time | 8:00-20:00 UTC |
| Website | QA/Fedora_17_test_days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
What to test?
Today's installment of Fedora Test Day will focus on the SystemConfig tool Kdump.Kdump is a graphical user interface that allows the user to configure kernel crash dumping via kdump and kexec. .
More information about Kdump can be found at the Kdump web site.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
Prerequisite for Test Day
The following prerequisites are recommended:
- An updated Fedora 17 pre-release, Rawhide (tips on installing Rawhide below), or a SoaS Fedora 17 RC1 or SoaS nightly live image
- Your hardware profile uploaded to Smolt according to these instructions
How to test?
Live image
If you do not wish to alter your computer's existing software, you may download a non-destructive live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here for Fedora 17 RC1. The "SoaS" image is the one you want to download
Test Cases
All test cases in as below:
- QA:Testcase_Kdump_Func_Default
- QA:Testcase_Kdump_Func_Halt
- QA:Testcase_Kdump_Func_Shell
- QA:Testcase_Kdump_Func_Reboot
- QA:Testcase_Kdump_Func_NFS
- QA:Testcase_Kdump_Func_SSH_Filter
- QA:Testcase_Kdump_Func_DebugMem
- QA:Testcase_Kdump_Func_CrasherBug
- QA:Testcase_Kdump_Func_Preextra_Bins_Modules
- QA:Testcase_Kdump_Func_Postextra_Bins_Modules
Test Results
If you have problems with any of the tests, report a bug to Bugzilla usually for the [1]. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the result template to enter your result, as shown in the example result line.
- IMPORTANT Memory Required for F17 & Testing in Virtualbox of anaconda (liveinst) 1024 minimum should be used
Message that 769 MB memory is required. (I have been told that this is hard wired in anaconda)
| User | Smolt Profile | Default | Halt | Shell | Reboot | NFS | SSH Filter | DebugMem | CrasherBug | Pre Extra Bins Modules | Post Extra Bins Modules |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Sample User | HW |  |
 |
 |
|
|
|
|