(add me to Dramatis Personae) |
|||
| Line 17: | Line 17: | ||
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ... | The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ... | ||
* Development - [[User:Harald | Harald Hoyer]] | * Development - [[User:Harald | Harald Hoyer]] | ||
* Quality Assurance - [[User:dkovalsk | David Kovalsky]], [[User:hondra | Ondrej Hudlicky]], [[User:jlaska | James Laska]] | * Quality Assurance - [[User:dkovalsk | David Kovalsky]], [[User:hondra | Ondrej Hudlicky]], [[User:jlaska | James Laska]], [[User:Adamwill|Adam Williamson]] | ||
= Prerequisite for Test Day = | = Prerequisite for Test Day = | ||
Revision as of 23:28, 17 February 2009
| DATE | TIME | WHERE |
| 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:
Who's available
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)
- 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
- tip1: try F11 Alpha + updates if rawhide doesn't install
- tip2: install F10 + rawhide updates if F11 Alpha doesn't install on your machine
- tip3: yum --skip-broken may come in handy in case there are broken deps `yum --skip-broken update'
Test
Follow each of the test cases: https://fedoraproject.org/wiki/Category:Bootchart_Test_Cases
Optionally, perform the testing with different configurations, particularly with different filesystems - we are interested in results with ext3, ext4, and xfs.
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.
Results
| User | Smolt Profile | Bootchart - my setup | Bootchart - desktop | Bootchart - server | Bootchart - minimal | Comments |
|---|---|---|---|---|---|---|
| User:SampleUser | ||||||
| David Kovalský | HW | |||||
| Adam Williamson | HW | 27s RA: 27s | 25s RA: 27s | 31s RA: 29s | 23s RA: 21s | Core 2 Quad Q6600 @ 3.34GHz, 4GB, ext4 |
Advanced Test Plan
Various issues may affect the performance of boot, especially readahead and file system.
11) Install readahead, and for every setup (desktop, server, minimal) first boot for the first time, let it gather it's data and then reboot with readahead on (chkconfig readahead on). Upload the bootchart into the same table with the name set to Bootchart-$UUID-server-ra.tgz (same for desktop and minimal)
12) Boot into a complete desktop with Firefox. You will need to:
- patch bootchartd to wait for Firefox to start. Use this patch
- enable desktop services
- enable auto-login
- start Firefox in the login script
- reboot
- Again, provide bootchart data with and without readahead. Use Bootchart-$UUID-desktop-FF' (and optinally append filesystem and readahead info)
13) Try installing with ext4 filesystem and XFS filesystem. Reboot, and upload bootchart data:
- Bootchart-$UUID-server-ra-xfs or Bootchart-$UUID-minimal-ext4.
14) Got an idea of what's affecting your system boot? Try it out and say so in the comments :)
15) Got a different system than Fedora Rawhide? We're interested in your results too! Use the table below:
Results (other distros)
| User | Smolt Profile | Bootchart data | Distro | Enabled services | Comments |
|---|---|---|---|---|---|
| User:SampleUser | |||||
| Adam Williamson | HW | 24s | Mandriva Cooker 2009/02/13 | Equivalent to my Fedora services | Same machine as in Fedora chart. ext3 |