From Fedora Project Wiki

Revision as of 23:09, 19 March 2011 by Jskarvad (talk | contribs)

Fedora Test Days
Echo-testing-48px.png
Power Management

Date 2011-03-24
Time all day

Website QA/Fedora_15_test_days
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
Can't make the date?
If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

Instructions bellow are incomplete, this page will be finalized: 2011-03-20

What to test?

Today's instalment of Fedora Test Day will focus on Power Management

Who's available

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

Note: jskarvad will be available during CET business hours (UTC+1) on #fedora-test-day, #fedora-power, #fedora-devel, otherwise he will be on e-mail with non guaranteed response time.

Prerequisite for Test Day

Typing convetions

In the following text commands that needs to be run as root are prefixed by #, e.g.:

# id

means to run id command under the root account. Commands prefixed by $ do not need to be run under the root account.

How to test?

Focus on pm-utils, powertop, tuned. Some test cases are only for laptop users and it is signalled in test case description field. If you do not have laptop just skip them. You can also skip other test cases (e.g. if you do not have enough time). In this case just leave the columns for skipped test cases blank. Please note that your report will be still valuable even if you do not finish all test cases. Procedure:

  • Run test cases bellow
  • Report results to the result table

Prepare your system

Install the PM Test Day support package that will setup your system for this test day. It will install all required dependencies, packages and utilities. It will also setup your system to use the PM Test Day repo. This repo contains temporal fixes for bugs discovered and resolved shortly before test day (these fixes will get into F15 soon).

  1. Install the public key by:
    # rpm --import http://jskarvad.fedorapeople.org/RPM-GPG-KEY-pm-test-day
  2. Install the PM Test Day support package by:
    # yum install http://jskarvad.fedorapeople.org/pm-test-day-1-1.fc15.x86_64.rpm

Or you can skip the public key installation step and directly install the PM Test Day support package by:

  1. # yum install --nogpgcheck http://jskarvad.fedorapeople.org/pm-test-day-1-1.fc15.x86_64.rpm
    • This procedure will also install the public key which will be then used for verification of packages from the PM Test Day repo.

Finally make sure you have all current updates (and temporal fixes) installed by:

# yum update

Test Cases

  1. QA:Testcase_Power_Management_pm_suspend - pm-utils suspend
  2. QA:Testcase_Power_Management_pm_hibernate - pm-utils hibernate
  3. QA:Testcase_Power_Management_pm_bugreport - pm-utils bug-reporting tool
  4. QA:Testcase_Power_Management_pm_powersave - pm-utils powersave
  5. QA:Testcase_Power_Management_Lid_Close - Lid close
  6. QA:Testcase_Power_Management_powertop2_basic - PowerTOP 2.x basic
  7. QA:Testcase_Power_Management_powertop2_power_estimation_engine - PowerTOP 2.x power estimation engine
  8. QA:Testcase_Power_Management_powertop2_suggestions - PowerTOP 2.x suggestions
  9. QA:Testcase_Power_Management_tuned_basic - Tuned basic
  10. QA:Testcase_Power_Management_tuned_powersave_idle - Tuned laptop-battery-powersave profile, active idle
  11. QA:Testcase_Power_Management_tuned_powersave_load - Tuned laptop-battery-powersave profile, load
  12. QA:Testcase_Power_Management_tuned_performance_idle - Tuned throughput-performance profile, active idle
  13. QA:Testcase_Power_Management_tuned_performance_load - Tuned throughput-performance profile, load

Test Results

If you have problems with any of the tests, report a bug to Bugzilla usually for the component pm-utils, or powertop, or tuned. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the result template to enter your result, as shown in the example result line.

User Smolt Profile pm-suspend pm-hibernate pm-bugreport bugreport.txt pm-powersave PowerTOP 2.x basic PowerTOP 2.x PE engine PowerTOP 2.x suggestions Tuned basic Tuned psave idle Tuned psave load Tuned perf idle Tuned perf load References
Sample User HW
Pass pass
Pass pass
Warning warn
[1]
URL
Pass pass
Fail fail
[2]
Pass pass
Pass pass
1234 1234 1234 1234
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345