New issue
Advanced search Search tips

Issue 914478 link

Starred by 1 user
Status: Assigned
Owner:
achuith@chromium.org
Cc:
steve...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

cros chrome-sdk --use-external-config may use the sdk for internal.

Project Member Reported by osh...@chromium.org, Dec 12 
It only checks the version when looking for a cache,
and doesn't check full vs release. As a result, 
once release version is fetched, it silently uses
the release version even if --use-external-config is
specified.

Comment 1 by achuith@chromium.org, Dec 12 

--use-external-config uses the full builders (daisy-full, etc), and without it, we use the release builders (daisy-release, etc). We store the SDK version without keeping track of the source of the SDK. So if we download the internal version then immediately use --use-external-config, we'll find a version match in the cache instead of downloading from the external builder. So we end up using the internal version.

The workaround is to use --clear-sdk-cache whenever you switch usage of --use-external-config to force the SDK fetch.
►

Sign in to add a comment