New issue
Advanced search Search tips

Issue 807067 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Use the data we have about test lengths partners are experiancing to order the test queue

Project Member Reported by haddowk@chromium.org, Jan 29 2018

Issue description


We know which tests take the longest to run from data recieved in CPCon.

We can order the way that jobs get created in the database when a suite is expanded by changing the TEST_LENGTH

Use this data to attempt to schedule the longest running test, or tests that require special resources ( lighting, no loopback etc ) before the other tests to better utilize the DUT's and reduce the total time for CTS test execution for partners.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Jan 30 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/autotest-cheets/+/205591a8543a35e0ddcf0e033d3bffd123220526

commit 205591a8543a35e0ddcf0e033d3bffd123220526
Author: Keith Haddow <haddowk@chromium.org>
Date: Tue Jan 30 06:51:54 2018

Status: Fixed (was: Assigned)
Project Member

Comment 3 by bugdroid1@chromium.org, Feb 16 2018

Labels: merge-merged-release-R65-10323.B
The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/autotest-cheets/+/f95b8245d4601b14cfff6dd5ad755e9b01b7da99

commit f95b8245d4601b14cfff6dd5ad755e9b01b7da99
Author: Keith Haddow <haddowk@chromium.org>
Date: Fri Feb 16 23:31:55 2018

Sign in to add a comment