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

Issue 850740 link

Starred by 1 user
Status: Assigned
Owner:
█ bhthompson@chromium.org
Last visit > 30 days ago
Cc:
englab-sys-cros@google.com
█ josa...@chromium.org
█ bhthompson@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Add HWTest for vayne

Reported by jrbarnette@chromium.org, Jun 7 2018 
There are 16 vayne DUTs in the test lab, but the nami-release
builder is not configured to run BVT for any model.  The DUTs
have been sitting idle for quite some time (probably weeks).

We should configure nami-release to run HWTest for vayne ASAP.
Today is already too late.

Comment 1 by bhthompson@google.com, Jun 7 2018

Owner: bhthompson@google.com
Status: Fixed (was: Untriaged)
HWTest should be enabled for all Nami derivatives, I just made the setting, it will take an hour to go through the config_updater builder.

Comment 2 by jrbarnette@chromium.org, Jun 8 2018

Status: Assigned (was: Fixed)
Checking the most recent canaries, HWTest still hasn't been enabled
for nami-release.

Comment 3 by jrbarnette@chromium.org, Jun 8 2018 

... Checking bvt pool status, I do see that the release branches have enabled
testing; it appears the problem is restricted to the canary.

Comment 4 by johndhong@chromium.org, Jun 11 2018

Cc: englab-sys-cros@google.com

Comment 5 by benhenry@chromium.org, Aug 2

Owner: bhthompson@chromium.org

Comment 6 by jclinton@chromium.org, Dec 12

Components: -Infra>Client>ChromeOS>CI
►

Sign in to add a comment