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

Issue 715844 link

Starred by 1 user
Status: Fixed
Owner:
█ sidal@chromium.org
Last visit > 30 days ago
Closed: Sep 2017
Cc:
█ vineeths@chromium.org
█ jean@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Extend default times for hwqual and storage qual to effectively unlimited

Project Member Reported by haddowk@chromium.org, Apr 27 2017 

Hardware Qual and Storage Qual tests run for days and weeks.

They are run from moblab exclusively - there is no value in having these tests time out as the partner has to remember to change the timeout every time they run a test.

A partner can always manually "time out" the test by aborting it if they choose.

Extend the timeout for these suites/tests to a value that is long enough that they never interrupt a test.

Reported by partner @
Project Member

Comment 1 by bugdroid1@chromium.org, Jun 8 2017 

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

commit f885e8a2b828fb149233aba73656309db2431eac
Author: Keith Haddow <haddowk@chromium.org>
Date: Thu Jun 08 17:10:55 2017

[autotest] When waking up moblab DUTs send more than one ping.

We see the wrong IP addresses coming back when we send fping packets
to wake up the device.  It is a shot in the dark to send more than
one ping but low overhead.

BUG= chromium:715844 
TEST=test_that on local moblab

Change-Id: Iaa506d4394afe5b1770408e4edfc3f41ca5269c2
Reviewed-on: https://chromium-review.googlesource.com/524233
Commit-Ready: Keith Haddow <haddowk@chromium.org>
Tested-by: Keith Haddow <haddowk@chromium.org>
Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org>
Reviewed-by: Keith Haddow <haddowk@chromium.org>

[modify] https://crrev.com/f885e8a2b828fb149233aba73656309db2431eac/server/hosts/moblab_host.py

Comment 2 by haddowk@chromium.org, Aug 31 2017

Labels: OS-Chrome
Owner: sidal@chromium.org

Comment 3 by sidal@chromium.org, Sep 6 2017

Status: Fixed (was: Assigned)
Default time is extended to 4 weeks. Should be more than enough for mem_qual and storage_qual.
Project Member

Comment 4 by bugdroid1@chromium.org, Sep 9 2017 

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

commit 266e400af9dcf02a5f4235bd6e180d017e1598c1
Author: Sida Liu <sidal@chromium.org>
Date: Sat Sep 09 00:36:07 2017

Fix hardware test suites timeout:

1) Set entire suite timeout to 28 days
2) Set individual test timeout to 28 days
3) affect the following test suites:

	a) hardware_memoryqual
	b) hardware_memoryqual_quick
	c) hardware_storagequal
	d) hardware_storagequal_quick

BUG= chromium:715844 
TEST=Ran the test suites on DUT

Change-Id: I495ce5e83c3986c795b3a9d3d6540106e898c865
Reviewed-on: https://chromium-review.googlesource.com/648644
Commit-Ready: Sida Liu <sidal@chromium.org>
Tested-by: Sida Liu <sidal@chromium.org>
Reviewed-by: Sida Liu <sidal@chromium.org>
Reviewed-by: Michael Tang <ntang@chromium.org>

[modify] https://crrev.com/266e400af9dcf02a5f4235bd6e180d017e1598c1/test_suites/control.hardware_memoryqual
[modify] https://crrev.com/266e400af9dcf02a5f4235bd6e180d017e1598c1/test_suites/control.hardware_storagequal_quick
[modify] https://crrev.com/266e400af9dcf02a5f4235bd6e180d017e1598c1/test_suites/control.hardware_memoryqual_quick
[modify] https://crrev.com/266e400af9dcf02a5f4235bd6e180d017e1598c1/test_suites/control.hardware_storagequal

Comment 5 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Comment 6 by dchan@chromium.org, Jan 23 2018

Status: Fixed (was: Archived)
►

Sign in to add a comment