cros deploy should warn when deploying to downloaded test images |
||
Issue descriptionFollow the go/simplechrome workflow, download and install an unsigned test image, hack on chrome. Setup chroot. cros_workon start crash-reporter emerge-link crash-reporter cros deploy <ip> crash-reporter Get this failure message: RunCommandError: return code: 1; command: ssh -p 22 '-oConnectionAttempts=4' '-oUserKnownHostsFile=/dev/null' '-oProtocol=2' '-oConnectTimeout=30' '-oServerAliveCountMax=3' '-oStrictHostKeyChecking=no' '-oServerAliveInterval=10' '-oNumberOfPasswordPrompts=0' '-oIdentitiesOnly=yes' -i /tmp/ssh-tmp3ReZ_o/testing_rsa root@172.18.37.56 -- 'FEATURES=-sandbox' 'PORTAGE_CONFIGROOT=/usr/local' "CONFIG_PROTECT='-*'" 'PKGDIR=/usr/local/tmp/cros-deploy/tmp.pzcd6dbnC7/packages' 'PORTDIR=/usr/local/tmp/cros-deploy/tmp.pzcd6dbnC7' 'PORTAGE_TMPDIR=/usr/local/tmp/cros-deploy/tmp.pzcd6dbnC7/portage-tmp' emerge --usepkg /usr/local/tmp/cros-deploy/tmp.pzcd6dbnC7/packages/chromeos-base/crash-reporter-9999.tbz2 '--root=/' cmd=['ssh', '-p', '22', '-oConnectionAttempts=4', '-oUserKnownHostsFile=/dev/null', '-oProtocol=2', '-oConnectTimeout=30', '-oServerAliveCountMax=3', '-oStrictHostKeyChecking=no', '-oServerAliveInterval=10', '-oNumberOfPasswordPrompts=0', '-oIdentitiesOnly=yes', '-i', '/tmp/ssh-tmp3ReZ_o/testing_rsa', 'root@172.18.37.56', '--', 'FEATURES=-sandbox', 'PORTAGE_CONFIGROOT=/usr/local', "CONFIG_PROTECT='-*'", 'PKGDIR=/usr/local/tmp/cros-deploy/tmp.pzcd6dbnC7/packages', 'PORTDIR=/usr/local/tmp/cros-deploy/tmp.pzcd6dbnC7', 'PORTAGE_TMPDIR=/usr/local/tmp/cros-deploy/tmp.pzcd6dbnC7/portage-tmp', 'emerge', '--usepkg', u'/usr/local/tmp/cros-deploy/tmp.pzcd6dbnC7/packages/chromeos-base/crash-reporter-9999.tbz2', '--root=/'], extra env={'LC_MESSAGES': 'C'} Scroll way back and find this other message: WARNING: One or more repositories have missing repo_name entries: /usr/local/tmp/cros-deploy/tmp.pzcd6dbnC7/profiles/repo_name NOTE: Each repo_name entry should be a plain text file containing a unique name for the repository on the first line. !!! CONFIG_PROTECT is empty !!! /usr/local/etc/portage/make.profile is not a symlink and will probably prevent most merges. !!! It should point into a profile within /usr/local/tmp/cros-deploy/tmp.pzcd6dbnC7/profiles/ !!! (You can safely ignore this message when syncing. It's harmless.) !!! Problem with sandbox binary. Disabling... !!! Problem resolving dependencies for /usr/local/tmp/cros-deploy/tmp.pzcd6dbnC7/packages/chromeos-base/crash-reporter-9999.tbz2 emerge: there are no ebuilds to satisfy "chromeos-base/libchrome:395517[cros-debug]". (dependency required by "chromeos-base/crash-reporter-9999::chromiumos" [binary]) (dependency required by "/usr/local/tmp/cros-deploy/tmp.pzcd6dbnC7/packages/chromeos-base/crash-reporter-9999.tbz2" [argument]) 09:36:31: ERROR: Failed to emerge package crash-reporter-9999.tbz2 The underlying issue is that this is a downloaded test image (probably release build?) whereas I built crash-reporter myself (probably debug build?). There are a few problems here: * The last error from "cros deploy" isn't the actual problem * There are lots of "!!!!" errors that aren't the actual problem * I probably shouldn't be allowed to deploy to a downloaded image anyway
,
Feb 16 2017
the problem is that James installed a release image that is built w/out USE=cros-debug, and now he's trying to deploy packages from his local developer build that are built with USE=cros-debug. i don't know what "download and install an unsigned test image" means. there is no such thing as "unsigned" in the CrOS world -- everything is always signed. dev images are simply signed with well known dev keys.
,
Feb 17 2017
"unsigned" means go/goldeneye, click on a build, find your board, click "Images", click "unsigned test image". I guess the label is wrong in that UI? Regardless, it should would be nice if the "cros deploy" failure message was clearer.
,
Feb 17 2017
the error message isn't from cros deploy, it's from emerge you can set USE=-cros-debug locally and then rebuild things, and then you can deploy compatible packages. or deploy all the packages with USE=cros-debug.
,
Feb 17 2017
I'm not looking to use this workflow. I'm fine building my own image. I want an easy-to-understand error message when it goes wrong. This is a common problem in many on-device workflows I use. Specifically, everything you see in the last screen full of error messages is only tangentially related to the problem. The actual error is often 40+ lines above. There are also a variety of "normal" error messages you have to know to ignore. I would *love* something like a single line, somewhere in the last 40 lines, that says: "Error: Cannot emerge, your USE flags do not match, "cros-debug" not found. Are you trying to deploy to a release image?" Or something like that.
,
Aug 18 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by derat@chromium.org
, Feb 16 2017Components: -Infra>Client>ChromeOS OS>Packages