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

Issue 765741 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

ChromeOS canay bots failures due to "Missing recovery image"

Project Member Reported by osh...@chromium.org, Sep 15 2017

Issue description

This started on Sep 13 early morning builds.


@@@STEP_FAILURE@@@
05:55:23: ERROR: Traceback (most recent call last):
  File "/b/c/cbuild/repository/chromite/cbuildbot/stages/generic_stages.py", line 695, in Run
    self.PerformStage()
  File "/b/c/cbuild/repository/chromite/cbuildbot/stages/release_stages.py", line 46, in PerformStage
    raise InvalidTestConditionException('Missing recovery image.')
InvalidTestConditionException: Missing recovery image.


Here are boards that have this problem.

https://uberchromegw.corp.google.com/i/chromeos/builders/butterfly-release/builds/4064/steps/SignerTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/falco-release/builds/2827/steps/SignerTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/falco_li-release/builds/1599/steps/SignerTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/leon-release/builds/2311/steps/SignerTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/link-release/builds/5925/steps/SignerTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/lumpy-release/builds/5346/steps/SignerTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/mccloud-release/builds/1501/steps/SignerTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/monroe-release/builds/2115/steps/SignerTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/panther-release/builds/2119/steps/SignerTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/parrot-release/builds/4136/steps/SignerTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/parrot_ivb-release/builds/1500/steps/SignerTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/peppy-release/builds/2955/steps/SignerTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/stout-release/builds/4279/steps/SignerTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/stumpy-release/builds/5612/steps/SignerTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/tricky-release/builds/1500/steps/SignerTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/wolf-release/builds/2502/steps/SignerTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/zako-release/builds/1787/steps/SignerTest/logs/stdio

 

Comment 1 by xixuan@chromium.org, Sep 18 2017

Cc: puneetster@chromium.org
Owner: amstan@chromium.org
Assign to sheriff to see whether this happens again or is a big problem

Comment 2 by osh...@chromium.org, Sep 18 2017

Cc: x...@chromium.org
Status: Fixed (was: Untriaged)
Looks like this is fixed.

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

Status: Archived (was: Fixed)

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

Status: Fixed (was: Archived)

Sign in to add a comment