From Fedora Project Wiki
(Drop direct Test Days category membership) |
|||
| (5 intermediate revisions by 4 users not shown) | |||
| Line 78: | Line 78: | ||
| {{result|warn}} <ref>Works on 500M /boot, not enough space on 200M /boot - not preupgrade's fault.</ref> <ref>My mouse pointer is stuck while upgrading in anaconda. Re-occurring issue about frozen input devices in KVM?</ref> | | {{result|warn}} <ref>Works on 500M /boot, not enough space on 200M /boot - not preupgrade's fault.</ref> <ref>My mouse pointer is stuck while upgrading in anaconda. Re-occurring issue about frozen input devices in KVM?</ref> | ||
| {{result|none}} | | {{result|none}} | ||
| {{result|fail | | {{result|fail||587610|587627}} | ||
| {{result|pass}} <ref>Used bigger /boot than 200M (not possible with that), but simulated the test case idea with some filler files</ref> | | {{result|pass}} <ref>Used bigger /boot than 200M (not possible with that), but simulated the test case idea with some filler files</ref> | ||
| <references/> | | <references/> | ||
| Line 108: | Line 108: | ||
| [[User:ericb|ericb]] | | [[User:ericb|ericb]] | ||
| [http://smolts.org/client/show/pub_09370914-5864-4224-92c9-d70e0ceb3eab KVM guest] | | [http://smolts.org/client/show/pub_09370914-5864-4224-92c9-d70e0ceb3eab KVM guest] | ||
| {{result|warn}} <ref>Manually pruned 200M /boot from three down to one kernel, but preupgrade still complained that install.img didn't fit</ref> <ref>{{bz|567978}} - On first reboot, NetworkManager failed to detect network with both IPv4 and v6 requested, but worked fine with just IPv4 requested. Upgrade succeeded via network install.img.</ref> | | {{result|warn}} <ref>Manually pruned 200M /boot from three down to one kernel, but preupgrade still complained that install.img didn't fit</ref> <ref group="long">{{bz|567978}} - On first reboot, NetworkManager failed to detect network with both IPv4 and v6 requested, but worked fine with just IPv4 requested. Upgrade succeeded via network install.img.</ref> | ||
| {{result|none}} | | {{result|none}} | ||
| {{result|warn}} <ref>Attempt to download rawhide failed with no more mirrors to try; not sure if it was related to the expected disk full error</ref> | | {{result|warn}} <ref>Attempt to download rawhide failed with no more mirrors to try; not sure if it was related to the expected disk full error</ref> | ||
| {{result|fail}} <ref>After cleanup, df -h /boot reported 155M available, but preupgrade failed to download Fedora 13 branched with warning of checksum failure downloading vmlinuz; looks like {{bz|587610}}</ref> | | {{result|fail}} <ref group="long">After cleanup, df -h /boot reported 155M available, but preupgrade failed to download Fedora 13 branched with warning of checksum failure downloading vmlinuz; looks like {{bz|587610}}</ref> | ||
| <references/> | | <references/> | ||
|- | |- | ||
| Line 132: | Line 132: | ||
| [[User:japafi]] | | [[User:japafi]] | ||
| VirtualBox guest | | VirtualBox guest | ||
| {{result|fail}} <ref>/boot partition as set by default install (198337 1K-blocks/164751 available), but preupgrade still complained that install.img didn't fit. At that time there was 132257 1K blocks available</ref> | | {{result|fail}} <ref group="long">/boot partition as set by default install (198337 1K-blocks/164751 available), but preupgrade still complained that install.img didn't fit. At that time there was 132257 1K blocks available</ref>[http://www.smolts.org/client/show/pub_6f381837-cc13-457d-bb37-8fa97cea2a54 HW] | ||
| {{result|none}} | | {{result|none}} | ||
| {{result|warn}} <ref>Did the test with non-default /boot (400M). Adjusted available disk space accordingly. Got error message on "no more mirrors to try" when disk was full (Step #7 on the test case). The error message could be more accurate as the problem was not about network error, but disk space. Other than that, I would consider this as PASS.</ref> | | {{result|warn}} <ref group="long">Did the test with non-default /boot (400M). Adjusted available disk space accordingly. Got error message on "no more mirrors to try" when disk was full (Step #7 on the test case). The error message could be more accurate as the problem was not about network error, but disk space. Other than that, I would consider this as PASS.</ref> | ||
| {{result|none}} | | {{result|none}} [http://www.smolts.org/client/show/pub_6f381837-cc13-457d-bb37-8fa97cea2a54 HW] | ||
| <references/> | | <references/> | ||
|} | |} | ||
== Long comments == | |||
<references group="long" /> | |||
[[Category:Fedora 13 Test Days]] | |||
Latest revision as of 19:36, 26 June 2015
| DATE | TIME | WHERE |
| 2010-04-29 | All day | #fedora-test-day (webirc) |
What to test?[edit]
Today's installment of Fedora Test Day will focus on Preupgrade
Who's available[edit]
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[edit]
- A F11 or F12 system on bare metal or virtual machine
- Network connection
- The following packages updates installed
preupgrade-1.1.5-1.fc12su -c 'yum --enablerepo=updates-testing update preupgrade'
How to test?[edit]
Follow the test cases below to preupgrade your existing fedora 11 or 12 system.
Test Cases[edit]
- QA:Testcase_Preupgrade
- QA:Testcase_Preupgrade_from_older_release
- QA:Testcase_Preupgrade_low_/boot_disk_space_to_download
- QA:Testcase_Preupgrade_low_/boot_disk_space_to_install
Test Results[edit]
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 PASS. If you had trouble, enter the word FAIL, 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 | Smolt Profile | preupgrade | preupgrade older release | low space for download | low space for install | References |
|---|---|---|---|---|---|---|
| User:FasUser | HW |  |
 |
|||
| User:Rhe | kvm guest | |
||||
| jlaska | KVM guest | |
|
|
||
| kparal | KVM guest |  |
|
| ||
| gnat | HW | |
||||
| Austin | HW | |
||||
| Juan Rodriguez | Laptop | |
||||
| ericb | KVM guest | |
|
|
||
| gui1ty | HW | |
||||
| User:ivancjimenez | HW | |||||
| User:japafi | VirtualBox guest | |
|
Long comments[edit]
- ↑ RHBZ #567978 - On first reboot, NetworkManager failed to detect network with both IPv4 and v6 requested, but worked fine with just IPv4 requested. Upgrade succeeded via network install.img.
- ↑ After cleanup, df -h /boot reported 155M available, but preupgrade failed to download Fedora 13 branched with warning of checksum failure downloading vmlinuz; looks like RHBZ #587610
- ↑ /boot partition as set by default install (198337 1K-blocks/164751 available), but preupgrade still complained that install.img didn't fit. At that time there was 132257 1K blocks available
- ↑ Did the test with non-default /boot (400M). Adjusted available disk space accordingly. Got error message on "no more mirrors to try" when disk was full (Step #7 on the test case). The error message could be more accurate as the problem was not about network error, but disk space. Other than that, I would consider this as PASS.