Bug 1320605 - battery test fails when 100% charged
Summary: battery test fails when 100% charged
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Certification Program
Classification: Red Hat
Component: redhat-certification-hardware
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: brose
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-23 15:44 UTC by Doreen Alongi
Modified: 2017-04-19 02:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-19 02:16:45 UTC
Target Upstream Version:


Attachments (Terms of Use)
log file from failing battery test (848 bytes, text/plain)
2016-03-23 15:44 UTC, Doreen Alongi
no flags Details
log file from passing battery test (728 bytes, text/plain)
2016-03-23 15:45 UTC, Doreen Alongi
no flags Details

Description Doreen Alongi 2016-03-23 15:44:55 UTC
Created attachment 1139641 [details]
log file from failing battery test

Description of problem:

The battery test fails when run on a Toshiba Portege laptop when the battery starts out 100% charged.  If the battery is only 96% percent charged when the test starts then it passes.

Version-Release number of selected component (if applicable):

redhat-certification-hardware.noarch             1.7.1-20160311.el7
redhat-certification.noarch                      2.3-20160315.el7  

How reproducible: 100%


Steps to Reproduce:
1.run interactive battery test from webui to laptop
2.unplug power cord when asked to do so
3.Wait for failure

Actual results:

The test fails and the log files says 

Error: could not verify battery discharging

Expected results:

The test should pass and we should see

verified battery is discharging



Additional info:
see output.log file from failing and passing tests

Comment 1 Doreen Alongi 2016-03-23 15:45:45 UTC
Created attachment 1139642 [details]
log file from passing battery test


Note You need to log in before you can comment on or make changes to this bug.