|Thu February 19, 2009||From 12:00 to 20:00 UTC (7am -> 3pm ET)||#fedora-qa)|
What to test?
Today's instalment of Fedora Test Day will focus on:
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
- Development - Harald Hoyer
- Quality Assurance - David Kovalsky, Ondrej Hudlicky, James Laska, Adam Williamson
Prerequisite for Test Day
- Rawhide fully updated (some tips below). Remember, Rawhide is an unsupported development branch: use an installation you don't mind getting broken.
- FAS Account - you can create an account in 3 minutes if you don't have one
- Selinux enabled. If you need to run in permissive mode please file a bug against selinux
How to test?
Update your machine to latest Rawhide
See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide.
Follow each of these test cases:
A more advanced test case is optional:
Optionally, perform the testing with different configurations, particularly with different filesystems - we are interested in results with ext3, ext4, and xfs.
Optionally, test with another distribution, ideally on the same system and with a similar range of services for comparison.
Send in your results
Upload the files generated as you ran the test cases. You will get an error page after each file upload - don't worry, this is normal. After performing the upload, go to the File list page and you will see your upload at the top of the list. The URL to use when you add it to the table is the one labelled '(file)'.
To fill in the table, use an existing line - like Adam Williamson's - as a model. The first column should be your name, with a link to your User: page, or perhaps your email or IRC nick if you don't have a useful User: page. The second column should be a link to your profile page on Smolt - you should have got this URL when you uploaded your hardware profile to Smolt as you performed the tests. The remaining columns, except the last, should contain links to the files you just uploaded: both the readahead and non-readahead files for each test case. If you generated images, you can see how long each case took and use that time as the text for the link, as in Adam Williamson's entry. The last column is for notes.
If you are having trouble with the table, just ask for help in IRC.
Now you're finished! Take a look into the bootcharts and identify bottlenecks. Use the notes section for simple notes, or services like http://www.pastebin.com if you want to add more information about your hardware. If you find any bugs, or have ideas how to improve the boot experience, file a bug into Red Hat Bugzilla.
The test day is divided into 2 parts - first part is about gathering the data. In the second part we're going to go through the data and prepare a report.
|User||Smolt Profile||Bootchart - my setup||Bootchart - desktop||Bootchart - server||Bootchart - minimal||Bootchart - full desktop||Comments|
|David Kovalský||HW||38s RA: 36s||Intel P4 @ 3.2GHz (HT enabled), 2GB, ext3|
|Adam Williamson||HW||27s RA: 27s||25s RA: 27s||31s RA: 29s||23s RA: 21s||Core 2 Quad Q6600 @ 3.34GHz, 4GB, ext4|
|Martin Sourada||HW||40s RA: 38s||46s RA: 44s||52s RA: 51s||40s RA: 40s||1m21s RA: 1m16s||Celeron M420 @ 1.6GHz, 1.5GB, ext3|
Results (other distros)
|User||Smolt Profile||Bootchart data||Distro||Enabled services||Comments|
|Adam Williamson||HW||24s||Mandriva Cooker 2009/02/13||Equivalent to my Fedora services||Same machine as in Fedora chart. ext3|