Methodology

How test are run?

In respond to a mail from Kir, some details about scenarios:

A basic 'patch' test looks like:
o build the appropriate kernel (2.6.16-026test014-x86_64-smp for
                                example)
o reboot
o run test

For test inside a 'guest' I just do something like:
o build the appropriate kernel (2.6.16-026test014-x86_64-smp for
                                example)
o reboot
o build the utilities (vztcl+vzquota for example)
o create a guest
o reboot
o launch a guest
o run the test in the guest

- The results are the average value of several iterations of each set of
these kind of tests. I will try to update the site with the numbers of
iterations behind each values.
- For the filesystem testing, the partition is not reformatted. I can
change this behaviour...
- For the settings of the guest I tried to use the default settings
(I had to change some openvz guest settings) just following the HOWTO on
vserver or openvz site.
For the kernel parameters, did you mean kernel config file tweaking?
- Cron are stopped during tests.
- All binaries are always build in the test node.