New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 819193 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Apr 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Add platform_BootUpTime to autotest

Reported by kasaiahx...@intel.com, Mar 6 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36

Steps to reproduce the problem:
Device converts the device into normal mode and checks the boot time.
1. Boot the device using reboot or lid close/open
2. Check the boot time 

What is the expected behavior?

What went wrong?
Adding new TC to check the boot time.

Did this work before? N/A 

Chrome version:   Channel: n/a
OS Version: 
Flash Version:
 
Cc: kmshelton@chromium.org ka...@chormium.org
this seems like a description of a test case put into a bug template.  Please provide more context.
As I am not able to edit the bug, giving comment here.

Test will check the boot up time when the device is booted from normal mode. The boot up time should be <= 8 Secs.

Test Steps:
1. Boot the chromebook using reboot/lid_close_open and check the boot up time

Criteria: Fail if the boot up time is more than 8 secs.


I meant one level higher of context, like: what is motivating this test case? e.g. is this from a particular project?

Doesn't lid_close_open send a device to S3? I don't think 8 seconds is the performance requirement for S3 to S5
As device is not logged in, lid_close_open sends the device into S5 and calculating the device boot up time from S5->S0. Usually, the boot up time should be less than 8 secs in normal boot.
Cc: chromeos-performance@google.com
I see re: S5 when the DUT is logged out.

What about the higher level of context like whether a particular project is motivating adding this test case?

Is anyone from chromeos-performance@ equipped to review https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/951025?
Each customer design that we have enabled has had this requirement, hence this is part of our test suite. We’ll be happy to get more feedback from the performance team and add this test case.
Project Member

Comment 7 by bugdroid1@chromium.org, Apr 5 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/405166a9819658ae10bb9628ef237ef8afd0fe97

commit 405166a9819658ae10bb9628ef237ef8afd0fe97
Author: Bogineni Kasaiah <kasaiahx.bogineni@intel.com>
Date: Thu Apr 05 03:55:35 2018

Autotest: Add test to convert to Normal mode and checks the boot time

Test case will perform the various boots reboot, lid close/open and
checks the boot times. If boot time is less than 8.0 secs then it will
fail the test case.

Bug= chromium:819193 
Test=Execute the below command to run the test

test_that -b $BOARD $DUT_IP power_BootUpTime.lid_close_open
test_that -b $BOARD $DUT_IP power_BootUpTime.reboot

Change-Id: I7ea2d57085b9bf7fcbee4ad501478c4aa6cf2baf
Signed-off-by: Bogineni Kasaiah <kasaiahx.bogineni@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/951025
Reviewed-by: Wai-Hong Tam <waihong@google.com>
Reviewed-by: Kalin Stoyanov <kalin@chromium.org>

[add] https://crrev.com/405166a9819658ae10bb9628ef237ef8afd0fe97/server/site_tests/power_BootUpTime/control.lid_close_open
[add] https://crrev.com/405166a9819658ae10bb9628ef237ef8afd0fe97/server/site_tests/power_BootUpTime/power_BootUpTime.py
[add] https://crrev.com/405166a9819658ae10bb9628ef237ef8afd0fe97/server/site_tests/power_BootUpTime/control.reboot

Status: Fixed (was: Unconfirmed)

Sign in to add a comment