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

Issue 630331 link

Starred by 1 user
Status: Duplicate
Owner:
█ dshi@chromium.org
Last visit > 30 days ago
Closed: Jul 2016
Cc:
█ vpalatin@chromium.org
akes...@chromium.org
█ keta...@chromium.org
haoweiw@chromium.org
█ jrbarnette@chromium.org
█ shchen@chromium.org
█ puneetster@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 1
Type: Bug



Sign in to add a comment

x86-alex_he-release builds failing for a while with "board:x86-alex_he" not found

Project Member Reported by snanda@chromium.org, Jul 21 2016 
x86-alex_he-release builds have been failing for over a month now, the last successful build was on May 28:
https://uberchromegw.corp.google.com/i/chromeos/builders/x86-alex_he-release


Failures are due to no suitable DUTs being found:
autoupdate_EndToEndTest_paygen_au_dev_delta_8530.24.0   [  INFO  ]
autoupdate_EndToEndTest_paygen_au_dev_delta_8530.24.0     TEST_NA: Label "board:x86-alex_he" not found

Attempting to display pool info: bvt
No hosts found for board:x86-alex_he in pool:bvt


Infra deputies could you investigate?

Comment 1 by dshi@chromium.org, Jul 21 2016

Cc: haoweiw@chromium.org jrbarnette@chromium.org
+Richard and Haowei (lab wrangler)

Did we remove all x86-alex_he in the lab? If so, should we disable hwtest and autest for x86-alex_he-release build?

Comment 2 by jrbarnette@chromium.org, Jul 21 2016

Mergedinto: 629094
Status: Duplicate (was: Unconfirmed)
To my knowledge, we've never had alex_he DUTs in the lab.

Moreover, the lack of DUTs isn't the cause of the failures;
by design, canaries do not fail when DUTs are missing.
Here's the real problem:
    PayloadTestError: cannot find source stateful.tgz for testing chromeos_8616.0.0_x86-alex-he_canary-channel_full_test.bin-d14d2262993c9ed6ad24572081055f2c

That's a known bug.
►

Sign in to add a comment