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

Issue 857149 link

Starred by 1 user
Status: Fixed
Owner:
█ jrbarnette@chromium.org
Last visit > 30 days ago
Closed: Jun 2018
Cc:
█ jachuang@chromium.org
ddavenp...@chromium.org
jclinton@chromium.org
█ bhthompson@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

grunt release builder should run HWTest

Project Member Reported by ihf@chromium.org, Jun 27 2018 
Strangely right now it doesn't do so, even thought I would think chromeos_config.py is set up right.

https://uberchromegw.corp.google.com/i/chromeos/builders/grunt-release

Comment 1 by djkurtz@google.com, Jun 28 2018

Cc: jclinton@chromium.org
Owner: jrbarnette@chromium.org
Status: (was: Untriaged)
Does this have the same root cause as issue 850738?  Or unique to grunt?
In any case, how do these tests get enabled for this builder?

Comment 2 by bhthompson@google.com, Jun 28 2018

Cc: jachuang@chromium.org
Status: Fixed
It looks like when the models were created in Goldeneye they had all their tests disabled, so this is probably the same as https://bugs.chromium.org/p/chromium/issues/detail?id=850738

I went through and enabled them all on all grunt models so they should run on the build following when exist in the lab. 

Presuming this is fixed.
►

Sign in to add a comment