Test Day:2009-04-02 Power management: Difference between revisions

Revision as of 11:31, 31 March 2009

DATE	TIME	WHERE
Thu May 02, 2009	From 12:00 to 00:00 UTC (7am -> 7pm ET)	#fedora-qa)

What to test?

Today's instalment of Fedora Test Day will focus on:

Features/PowerManagement

Who's available

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

Development
- Phil Knirsch <pknirsch@redhat.com> - (Lead, tuned, monitoring, documentation)
- Jiri Skala <jskala@redhat.com> - (BLTK packager)
- Marcela Maslanova <mmaslano@redhat.com> - (initscript/udev service start/stop automation)
Quality Assurance
- Jan Scotka <jsotka@redhat.com>
- Karel Volny <kvolny@redhat.com>
- Yulia Kopkova <ykopkova@redhat.com>

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

no animals will be hurt during testing

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.

Make sure powertop is installed on your machine.

The tests can be run in various levels of accuracy depending on your system and additional equipment. For laptops the tests should be run on battery power so powertop can record the power usage. For normal systems use of a wattmeter like the ones from Watts Up can help record the power usage instead.

Run powertop -d
Run powertop -d on battery mode (laptops only)
Run powertop -d with a wattmeter

Additionally if you install kernel-devel and kernel-debuginfo you can additionally install tuned-utils and run additional monitoring tools:

Run diskdevstat
Run netdevstat

The results of those can be combined with the results from the various powertop runs.

For automated recording we've written a script that checks for the various tools necessary to record the results and saves the available results in several files and makes a tarball of them via your system-id.

Additionally in case you don't want to do the upload the script will output a summary of the results which you can just copy and paste into the wiki page here as well.

Test

The following testcases are available:

QA:Testcase_powermanagemt_personal
QA:Testcase_powermanagemt bluetooth
QA:Testcase_powermanagemt init1

In progress [ 50% ]
- Need to find proprer way how to test it.
  - powertop - main utility to collect data about process
  - acpi - used in bltk (battery life toolkit, which is good for performance of some type of stress (reader, developer, office, idle)
- What measure
  - More exact measurement in init runlevel 1
    - Written some scripts to test it
      - bzip2 test
      - dd copy test from /dev/zero
      - vsftpd test witl localhost lftp client
    - Idle test of bltk in runlevel 1
  - In runlevel 5
    - Other bltk stress (reader, office) usage - need fully charged battery
old # Plautrba testcase for testing of bluetooth on demand
- - computer tuned up and not tuned

Send in your results

Results

User	Smolt Profile	Output file	Comments
User:SampleUser

@@ Line 63: / Line 63: @@
   [[QA:Testcase_powermanagemt_personal]]
-  [http://plautrba.fedorapeople.org/bluez/how-to-test.txt Plautrba testcase for testing of bluetooth on demand]
+  [https://fedoraproject.org/wiki/QA/Test_Days/2009-04-02/PowerManagementBluez QA:Testcase_powermanagemt bluetooth]
   [https://fedoraproject.org/wiki/QA/Test_Days/2009-04-02/PowerManagementInit1Testcase QA:Testcase_powermanagemt init1]
@@ Line 79: / Line 79: @@
 *** In runlevel 5
 **** Other bltk stress (reader, office) usage - need fully charged battery
+* old # [http://plautrba.fedorapeople.org/bluez/how-to-test.txt Plautrba testcase for testing of bluetooth on demand]
 *** computer tuned up and not tuned

Search