Test Day:2009-10-22 Power Management

DATE	WHEN	WHERE
2009-10-22	From 12:00 to 21:00 UTC (8am -> 5pm EDT)	#fedora-test-day (webirc)

What to test?

For "Extended tuned"

• yum install tuned
• service tuned start
• cpu, disk and net devices should adapt to usage (monitor using strace e.g.)**

For "System tuning configuration and profiles"

• Run the new system tuning tool and list the different available profiles using:
  • tuned-adm list
• Run the new system tuning tool and select one of the profiles. Restart the machine afterwards and make sure the profile is being used at startup
  • tuned-adm modes laptop-battery-powersave
  • tuned-adm modes default
  • tuned-adm modes throughput-performance

For "New tool to measure improvements to system configuration changes or application changes"

• yum install tuned-utils
• run scomes
• change system settings
• run scomes again
• compare restults

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

• Development - Phil Knirsch, Marcela Maslanova (marcela on irc), Petr Lautrbach, Jiri Skala (skalnik on irc)
• Quality Assurance - David Pravec (dpravec), Jan Scotka

Prerequisite for Test Day

• A system with a network connection
• Rawhide (tips on installing Rawhide below)
• The rpm file will be prepared to install all test cases included necessary dependencies. Before installation of this package you need to allow debuginfo for rawhide in /etc/yum.repos.d/fedora-rawhide.repo

Download rpm and run:

* yum localinstall testday-pm-0.1-1.fc12.noarch.rpm

For scomes test you need to have the same version of kernel and kernel-debuginfo.

* uname -a
* rpm -q kernel-debuginfo

• Your hardware profile uploaded to Smolt according to these instructions

How to test?

Update your machine

See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:

Test Cases

The test cases are split into test groups. Some of the tests are a bit time-consuming. Please perform as many tests as possible. If you aren't able to run them all, please remember that the tests in each table are sort by importance in descending order.

X Window System

Estimated time: ?? minutes

These tests should be performed on all systems with X11 (desktop, laptops).

TestCase	Description	Extra Requirements
QA:Testcase_Power_Management_personal	Typical use of computer (Do whatever you are doing usually)	?
QA:Testcase_Power_Management_scomes	Measuring and collecting data with scomes tool	tuned-utils, kernel-debuginfo

Single mode

Estimated time: ?? minutes

These tests should be performed on all systems (desktop, laptop, servers). As you will have to reboot into single mode, install all required packages before. We recommend running the tests in sequence to refrain more reboots.

TestCase	Description	Extra Requirements
QA:Testcase_Power_Management_Tuned	Measuring differencies with and without tuned	?
QA:Testcase_Power_Management_init_1	Some measures in lowest runlevel. FTP working, copying of files, bzipping archive	?

Laptops

Estimated time: ?? minutes

Following tests are intended only for laptops. If you don't have a laptop, don't perform these tests because there is no easy way how to measure your system consumption. In addition you have to fully charge your battery.

TestCase	Description	Extra Requirements
QA:Testcase_Power_Management_bltk	3 workloads (Idle, OpenOffice, reader) measure power consumption of simulated reproducable load	OpenOffice is required during bltk installation, Firefox
QA:Testcase_Power_Management_tuned-adm	Measuring tuned profiles with bltk	tuned-adm, bltk and laptop

Test Results

Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. For example:

User	Smolt Profile	Sample test 1	Sample test 2	Sample test 3	Sample test 4	References
User:FasUser	HW	PASS	PASS	FAIL	PASS