| DATE | TIME | WHERE |
| 2010-09-02 | All day | #fedora-test-day (webirc) |
What to test?
Today's installation of Fedora Test Day will focus on Preupgrade
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Richard Hughes (IRC: hughsie)
- Quality Assurance - He Rui (IRC: rhe)
Prerequisite for Test Day
- A F-12 or F-13 system on bare metal or virtual machine
- Network connection
- The following packages updates installed:
preupgrade- F-12:
preupgrade-1.1.7-1.fc12.noarch - F-13: The newest version is available at http://people.freedesktop.org/~hughsient/fedora/13/i386. A scratch build is available for Fedora 13. You can install it by:
- F-12:
- # su -c 'yum --nogpgcheck localinstall "http://koji.fedoraproject.org/koji/getfile?taskID=2442952&name=preupgrade-1.1.7-0.20.20100902git.fc13.noarch.rpm"'
- python-urlgrabber
- F-12:
python-urlgrabber-3.9.1-4.2.fc12.noarch - F-13: The newest version is
python-urlgrabber-3.9.1-7.fc13, install it by:
- F-12:
- # su -c 'yum --enablerepo=updates-testing update python-urlgrabber'
How to test?
Follow the test cases below to preupgrade your existing fedora 12 or 13 system.
Test Cases
- QA:Testcase_Preupgrade - Enough /boot space to download and install
- QA:Testcase_Preupgrade_from_older_release - Not enough /boot space to download
- QA:Testcase_Preupgrade_cli - Preupgrade-cli and its command-line options
Test Results
If you have problems with any of the tests, report a bug to Bugzilla usually for the component preupgrade. If you are unsure about exactly how to file the report or what 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 describe the hardware (monitor, and optionally printer, scanner and colorimeter) you used to test. For each test case, if your system worked correctly, simply enter the word {{result|pass}}. If you had trouble, enter the word {{result|warn}}<ref>xxx</ref> or {{result|fail|bug number}}, with a footnote indicator, and put a link to the bug report in the References column (as in the example line). For tests you could not perform, enter a dash.
| User | preupgrade | preupgrade older release | preupgrade-cli | References |
|---|---|---|---|---|
| User:Example |  |
 |
||
| apetz |  |
N/A | N/A | |
| He Rui | [1] | [3] | ||
| newgle1 | ||||
| James Ni | [1] | N/A | N/A | |
| Epico | N/A | N/A | epico |
|
| jlaska | <ref> tag; name cannot be a simple integer. Use a descriptive title [1]
|
<ref> tag; name cannot be a simple integer. Use a descriptive title
|
<ref> tag; name cannot be a simple integer. Use a descriptive title
|
|
| Eric Blake | <ref> tag; name cannot be a simple integer. Use a descriptive title Cite error: Invalid <ref> tag; name cannot be a simple integer. Use a descriptive title [1] Cite error: Invalid <ref> tag; name cannot be a simple integer. Use a descriptive title [2]
|
<ref> tag; name cannot be a simple integer. Use a descriptive title [2]
|
<ref> tag; name cannot be a simple integer. Use a descriptive title Cite error: Invalid <ref> tag; name cannot be a simple integer. Use a descriptive title [2]
|
|
| User:RoyBoy626 | |
| ||
| Adam Miller | |
|
|
These were all done in KVM virtual machines with 1GB of ram and what appears to be plenty of space in /boot so my tests might have been skewed, but I didn't encounter any issues. |