Test Day:2009-10-22 Power Management: Difference between revisions

Revision as of 09:56, 15 October 2009

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

Under construction
The site is still under construction. Anything can change before the testday.

Purpose of this test

TODO
Some text here. ;)

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, 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

TODO
Upload new RPM, update its name, what about signing it?

Rawhide - development version of Fedora
Internet connection
The special-purpose Testday RPM package which includes necessary dependencies and provides all testing scripts.
- Download and install with: yum --nogpgcheck localinstall testday-pm-0.1-2.fc12.noarch.rpm
Kernel debugging info:
- Use debuginfo-install kernel or install it manually. (In case of manual installation you have to enable debug repository in /etc/yum.repos.d/fedora-rawhide.repo.)
- Versions of kernel and kernel-debuginfo must be the same. Please check it with:
  - uname -a
  - rpm -q kernel-debuginfo
Upload your hardware to Smolt according to these instructions.

Running the tests

Update your machine

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

Tests

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.

You don't have to download any special scripts for each test. Our Testday package provides following commands:

testday-run-testname (performing tests)
testday-pack-results (packing results of all tests in .tag.gz file)

Privileges
Please perform all tests as a regular user. Some tests require superuser permission. In these cases you will be informed by testing script.

X Window System

TODO
Create separate page for each test.

Estimated time: 12 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: 10 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: 20-35 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. You need to charge your battery before.

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

Test Results

TODO
Hmm. We have to change this.

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	PM Personal test	PM scomes test	PM tuned test	PM init1 test	PM BLTK test	PM tuned-adm test	References
User:FasUser	HW	2.40 Ghz 1.5% 2.14 Ghz 0.0% 1.87 Ghz 0.0% 1.60 Ghz 98.5% Wakeups-from-idle per second : 99.5 interval: 30.0s	PASS	FAIL ^[1]	2.40 Ghz 1.5% 2.14 Ghz 0.0% 1.87 Ghz 0.0% 1.60 Ghz 98.5% Wakeups-from-idle per second : 99.5 interval: 30.0s	PASS	PASS	↑ See RHBZ #12345

[1] See RHBZ #12345

[1]

@@ Line 7: / Line 7: @@
 |}
+{{admon/warning|Under construction|The site is still under construction. Anything can change before the testday.}}
-== WARNING! The site is still under construction ==
+== Purpose of this test ==
-== 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
+{{admon/warning|TODO|Some text here. ;)}}
 == Who's available ==
+The following cast of characters will be available testing, workarounds, bug fixes, general discussion ...
-The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
 * Development - [[User:Pknirsch|Phil Knirsch]], [[User:mmaslano|Marcela Maslanova]] (marcela on irc), [[User:Plautrba|Petr Lautrbach]], [[User:Jskala|Jiri Skala]] (skalnik on irc)
 * Quality Assurance - [[User:dpravec|David Pravec]] (dpravec), [[User:jscotka|Jan Scotka]]
-== Prerequisite for Test Day ==
+== Prerequisite ==
+{{admon/warning|TODO|Upload new RPM, update its name, what about signing it?}}
-* A system with a network connection
+* [[Releases/Rawhide|Rawhide]] - development version of Fedora
-* [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below)
+* Internet connection
-* The [http://mmaslano.fedorapeople.org/TestDay/testday-pm-0.1-2.fc12.noarch.rpm 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
+* The special-purpose [http://mmaslano.fedorapeople.org/TestDay/testday-pm-0.1-2.fc12.noarch.rpm Testday RPM package] which includes necessary dependencies and provides all testing scripts.
-Download rpm and run:
+** Download and install with: <code>yum --nogpgcheck localinstall testday-pm-0.1-2.fc12.noarch.rpm</code>
- * yum localinstall testday-pm-0.1-1.fc12.noarch.rpm
+* Kernel debugging info:
-For scomes test you need to have the same version of kernel and kernel-debuginfo.
+** Use <code>debuginfo-install kernel</code> or install it manually. (In case of manual installation you have to enable debug repository in <code>/etc/yum.repos.d/fedora-rawhide.repo</code>.)
- * uname -a
+** Versions of <code>kernel</code> and <code>kernel-debuginfo</code> must be the same. Please check it with:
- * rpm -q kernel-debuginfo
+*** <code>uname -a</code>
-* Your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions]
+*** <code>rpm -q kernel-debuginfo</code>
-* You need to be a root for tests and at the end of testing compress it with:
+* Upload your hardware to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions].
- * tar cfzv testday-091022.tar.bz2 /usr/local/testday-091022/
-and upload the file on the wiki.
-== How to test? ==
+== Running the tests ==
 === Update your machine ===
-See the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or:
+See the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide.
+=== Tests ===
-=== 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.
-<!-- Provide a list of test areas or test cases that you'd like contributors to execute.  For other examples, see [[:Category:Test_Cases]].
+You don't have to download any special scripts for each test. Our Testday package provides following commands:
--->
+* <code>testday-run-''testname''</code> (performing tests)
+* <code>testday-pack-results</code> (packing results of all tests in .tag.gz file)
-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.
+{{admon/important|Privileges|Please perform all tests as a regular user. Some tests require superuser permission. In these cases you will be informed by testing script. }}
 ==== X Window System ====
+{{admon/warning|TODO|Create separate page for each test.}}
 Estimated time: ''12 minutes''
@@ Line 133: / Line 114: @@
 === Test Results ===
+{{admon/warning|TODO|Hmm. We have to change this.}}
 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:

Search