"cros deploy <device> chromeos-chrome" to elm/kevin fails with 'arm not in IUSE' message |
||||||||
Issue descriptionBisection indicates that https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/930235 may be responsible. (cr) ((af6116340a8...)|BISECTING) rtownsend@machine /mnt/host/source/src/third_party/chromiumos-overlay $ cros deploy device chromeos-chrome 14:59:13: NOTICE: Cleaning outdated binary packages from /build/elm 14:59:15: NOTICE: These are the packages to emerge: 14:59:15: NOTICE: * 1) chromeos-base/chromeos-chrome-9999 [###############################################################################################################################################################################################################################################################################################################################------------------------------------------------------] 85%Exception during output capturing: RunCommandError('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-tmp1urfGT/testing_rsa\', \'root@10.1.27.105\', \'--\', \'FEATURES=-sandbox\', \'PORTAGE_CONFIGROOT=/usr/local\', "CONFIG_PROTECT=\'-*\'", \'PKGDIR=/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/packages\', \'PORTDIR=/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7\', \'PORTAGE_TMPDIR=/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/portage-tmp\', \'emerge\', \'--usepkg\', u\'/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/packages/chromeos-base/chromeos-chrome-9999.tbz2\', \'--root=/\'], extra env={\'LC_MESSAGES\': \'C\'}', <chromite.lib.cros_build_lib.CommandResult object at 0x7f79d54d8e50>, None) Captured stdout was: sending incremental file list chromeos-chrome-9999.tbz2 sent 99,686,833 bytes received 35 bytes 22,152,637.33 bytes/sec total size is 100,207,282 speedup is 1.01 *** emerging by path is broken and may not always work!!! Calculating dependencies ... done! >>> Emerging binary (1 of 1) chromeos-base/chromeos-chrome-9999::chromiumos * chromeos-chrome-9999.tbz2 size ;-) ... [ ok ] >>> Extracting info * Running stacked hooks for pre_pkg_setup * sysroot_build_bin_dir ... [ ok ] * Running stacked hooks for post_pkg_setup * python_eclass_hack ... [ ok ] >>> Extracting chromeos-base/chromeos-chrome-9999 >>> Installing (1 of 1) chromeos-base/chromeos-chrome-9999::chromiumos * Running stacked hooks for pre_pkg_preinst * wrap_old_config_scripts ... [ ok ] /usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/portage-tmp/portage/chromeos-base/chromeos-chrome-9999/temp/environment: line 20325: enewuser: command not found /usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/portage-tmp/portage/chromeos-base/chromeos-chrome-9999/temp/environment: line 20326: enewgroup: command not found * CHROME_DIR after installation * total 159M * -rwxr-xr-x 1 root root 98M Apr 12 14:52 chrome * -rw-r--r-- 1 root root 25M Apr 11 21:11 resources.pak * -rw-r--r-- 1 root root 11M Apr 11 21:11 chrome_200_percent.pak * -rw-r--r-- 1 root root 9.8M Feb 13 17:35 icudtl.dat * -rw-r--r-- 1 root root 4.7M Apr 11 21:11 chrome_100_percent.pak * -rwxr-xr-x 1 root root 3.2M Apr 11 22:13 nacl_helper_nonsfi * -rw-r--r-- 1 root root 3.0M Apr 11 21:43 nacl_irt_arm.nexe * -rwxr-xr-x 1 root root 2.6M Apr 12 14:51 libosmesa.so * -rw-r--r-- 1 root root 1.4M Apr 11 21:11 keyboard_resources.pak * -rw-r--r-- 1 root root 1.4M Apr 11 21:44 snapshot_blob.bin * -rwxr-xr-x 1 root root 1.1M Apr 12 14:51 nacl_helper * -rw-r--r-- 1 root root 182K Apr 11 18:14 natives_blob.bin * -rwxr-xr-x 1 root root 38K Apr 10 14:32 nacl_helper_bootstrap * -rw-r--r-- 1 root root 33K Feb 13 17:35 xdg-settings * -rwsr-xr-x 1 root root 19K Apr 12 14:51 chrome-sandbox * -rw-r--r-- 1 root root 5.0K Feb 13 17:32 chrome-wrapper * drwxr-xr-x 7 root root 4.0K Apr 12 14:52 . * drwxr-xr-x 3 root root 4.0K Apr 12 14:44 .. * drwxr-xr-x 2 root root 4.0K Apr 12 14:44 dbus * drwxr-xr-x 2 root root 4.0K Apr 12 14:44 locales * drwxr-xr-x 2 root root 4.0K Apr 12 14:44 plugins * drwxr-xr-x 2 root root 4.0K Apr 12 14:51 pnacl * drwxr-xr-x 4 root root 4.0K Apr 12 14:44 resources * -rw-r--r-- 1 root root 2.5K Feb 13 17:32 product_logo_48.png * CHROME_SIZE = 102072736 * ERROR: chromeos-base/chromeos-chrome-9999::chromiumos failed (preinst phase): * USE Flag 'arm' not in IUSE for chromeos-base/chromeos-chrome-9999 * * Call stack: * ebuild.sh, line 133: Called pkg_preinst * environment, line 20334: Called use 'arm' * phase-helpers.sh, line 200: Called die * The specific snippet of code: * die "USE Flag '${u}' not in IUSE for ${CATEGORY}/${PF}" * * If you need support, post the output of `emerge --info '=chromeos-base/chromeos-chrome-9999::chromiumos'`, * the complete build log and the output of `emerge -pqv '=chromeos-base/chromeos-chrome-9999::chromiumos'`. * The complete build log is located at '/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/portage-tmp/portage/chromeos-base/chromeos-chrome-9999/temp/build.log'. * The ebuild environment file is located at '/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/portage-tmp/portage/chromeos-base/chromeos-chrome-9999/temp/environment'. * Working directory: '/usr/local/lib/python2.7/site-packages' * S: '/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/portage-tmp/portage/chromeos-base/chromeos-chrome-9999/work/chromeos-chrome-9999' !!! FAILED preinst: 1 >>> Failed to install chromeos-base/chromeos-chrome-9999, Log file: >>> '/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/portage-tmp/portage/chromeos-base/chromeos-chrome-9999/temp/build.log' * Messages for package chromeos-base/chromeos-chrome-9999: * ERROR: chromeos-base/chromeos-chrome-9999::chromiumos failed (preinst phase): * USE Flag 'arm' not in IUSE for chromeos-base/chromeos-chrome-9999 * * Call stack: * ebuild.sh, line 133: Called pkg_preinst * environment, line 20334: Called use 'arm' * phase-helpers.sh, line 200: Called die * The specific snippet of code: * die "USE Flag '${u}' not in IUSE for ${CATEGORY}/${PF}" * * If you need support, post the output of `emerge --info '=chromeos-base/chromeos-chrome-9999::chromiumos'`, * the complete build log and the output of `emerge -pqv '=chromeos-base/chromeos-chrome-9999::chromiumos'`. * The complete build log is located at '/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/portage-tmp/portage/chromeos-base/chromeos-chrome-9999/temp/build.log'. * The ebuild environment file is located at '/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/portage-tmp/portage/chromeos-base/chromeos-chrome-9999/temp/environment'. * Working directory: '/usr/local/lib/python2.7/site-packages' * S: '/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/portage-tmp/portage/chromeos-base/chromeos-chrome-9999/work/chromeos-chrome-9999' Captured stderr was: 14:59:15: INFO: RunCommand: strip_package --sysroot /build/elm chromeos-base/chromeos-chrome-9999 [12/Apr/2018:14:59:16] BUILD Filtering install mask from chromeos-base/chromeos-chrome-9999 pbzip2: *WARNING: Trailing garbage after EOF ignored! 14:59:34: DEBUG: RunCommand: 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-tmp1urfGT/testing_rsa root@10.1.27.105 -- mkdir -p /usr/local/tmp/cros-deploy '&&' mktemp -d '--tmpdir=/usr/local/tmp/cros-deploy' 14:59:35: DEBUG: The temporary working directory on the device is /usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7 14:59:35: DEBUG: RunCommand: 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-tmp1urfGT/testing_rsa root@10.1.27.105 -- echo '${PATH}' 14:59:35: DEBUG: RunCommand: 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-tmp1urfGT/testing_rsa root@10.1.27.105 -- rm -rf /usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/packages/chromeos-base /usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/portage-tmp '&&' mkdir -p /usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/packages/chromeos-base /usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/portage-tmp 14:59:35: NOTICE: Copying chromeos-chrome-9999.tbz2 to device. 14:59:35: INFO: [mode:rsync] copy: /build/elm/stripped-packages/chromeos-base/chromeos-chrome-9999.tbz2 -> 10.1.27.105:/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/packages/chromeos-base 14:59:35: DEBUG: RunCommand: 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-tmp1urfGT/testing_rsa root@10.1.27.105 -- 'PATH=/usr/local/bin:/usr/local/sbin:$PATH rsync' --version 14:59:35: INFO: Using rsync compression: True Warning: Permanently added '10.1.27.105' (ED25519) to the list of known hosts. 14:59:39: INFO: Use portage temp dir /usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/portage-tmp 14:59:39: NOTICE: Installing chromeos-chrome-9999.tbz2. 14:59:39: INFO: RunCommand: 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-tmp1urfGT/testing_rsa root@10.1.27.105 -- 'FEATURES=-sandbox' 'PORTAGE_CONFIGROOT=/usr/local' "CONFIG_PROTECT='-*'" 'PKGDIR=/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/packages' 'PORTDIR=/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7' 'PORTAGE_TMPDIR=/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/portage-tmp' emerge --usepkg /usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/packages/chromeos-base/chromeos-chrome-9999.tbz2 '--root=/' Warning: Permanently added '10.1.27.105' (ED25519) to the list of known hosts. WARNING: One or more repositories have missing repo_name entries: /usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/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.74lzUUkLJ7/profiles/ !!! (You can safely ignore this message when syncing. It's harmless.) !!! Problem with sandbox binary. Disabling... 15:00:20: ERROR: Failed to emerge package chromeos-chrome-9999.tbz2 15:00:20: ERROR: Oops. Something went wrong. 15:00:20: ERROR: cros deploy failed before completing. 15:00:20: ERROR: <class 'chromite.lib.cros_build_lib.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-tmp1urfGT/testing_rsa root@10.1.27.105 -- 'FEATURES=-sandbox' 'PORTAGE_CONFIGROOT=/usr/local' "CONFIG_PROTECT='-*'" 'PKGDIR=/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/packages' 'PORTDIR=/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7' 'PORTAGE_TMPDIR=/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/portage-tmp' emerge --usepkg /usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/packages/chromeos-base/chromeos-chrome-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-tmp1urfGT/testing_rsa', 'root@10.1.27.105', '--', 'FEATURES=-sandbox', 'PORTAGE_CONFIGROOT=/usr/local', "CONFIG_PROTECT='-*'", 'PKGDIR=/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/packages', 'PORTDIR=/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7', 'PORTAGE_TMPDIR=/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/portage-tmp', 'emerge', '--usepkg', u'/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/packages/chromeos-base/chromeos-chrome-9999.tbz2', '--root=/'], extra env={'LC_MESSAGES': 'C'} Traceback (most recent call last): File "/mnt/host/source/chromite/lib/parallel.py", line 603, in TaskRunner task(*x, **task_kwargs) File "/mnt/host/source/chromite/lib/operation.py", line 176, in CaptureOutputInBackground func(*args, **kwargs) File "/mnt/host/source/chromite/cli/deploy.py", line 891, in _EmergePackages _Emerge(device, pkg_path, root, extra_args=emerge_args) File "/mnt/host/source/chromite/cli/deploy.py", line 775, in _Emerge capture_output=False, debug_level=logging.INFO) File "/mnt/host/source/chromite/lib/remote_access.py", line 1218, in RunCommand return super(ChromiumOSDevice, self).RunCommand(cmd, **kwargs) File "/mnt/host/source/chromite/lib/remote_access.py", line 1039, in RunCommand return self.BaseRunCommand(cmd, **kwargs) File "/mnt/host/source/chromite/lib/remote_access.py", line 986, in BaseRunCommand return self.GetAgent().RemoteSh(cmd, **kwargs) File "/mnt/host/source/chromite/lib/remote_access.py", line 345, in RemoteSh return cros_build_lib.RunCommand(ssh_cmd, **kwargs) File "/mnt/host/source/chromite/lib/cros_build_lib.py", line 658, in RunCommand raise RunCommandError(msg, cmd_result) 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-tmp1urfGT/testing_rsa root@10.1.27.105 -- 'FEATURES=-sandbox' 'PORTAGE_CONFIGROOT=/usr/local' "CONFIG_PROTECT='-*'" 'PKGDIR=/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/packages' 'PORTDIR=/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7' 'PORTAGE_TMPDIR=/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/portage-tmp' emerge --usepkg /usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/packages/chromeos-base/chromeos-chrome-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-tmp1urfGT/testing_rsa', 'root@10.1.27.105', '--', 'FEATURES=-sandbox', 'PORTAGE_CONFIGROOT=/usr/local', "CONFIG_PROTECT='-*'", 'PKGDIR=/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/packages', 'PORTDIR=/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7', 'PORTAGE_TMPDIR=/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/portage-tmp', 'emerge', '--usepkg', u'/usr/local/tmp/cros-deploy/tmp.74lzUUkLJ7/packages/chromeos-base/chromeos-chrome-9999.tbz2', '--root=/'], extra env={'LC_MESSAGES': 'C'}
,
Apr 25 2018
So when 'use arm' is called during pkg_preinst() in the build chroot, the contents of $PORTAGE_IUSE are: ^(accessibility|afdo\_chrome\_exp1|afdo\_chrome\_exp2|afdo\_use|alpha|amd64|amd64\-fbsd|amd64\-linux|app\_shell|arm|arm64|arm\-linux|asan|authpolicy|autotest|build\_native\_assistant|build\_tests|buildcheck|cfi|chrome\_debug|chrome\_debug\_tests|chrome\_internal|chrome\_media|chrome\_remoting|clang|clang\_tidy|component\_build|cups|debug\_fission|elibc\_AIX|elibc\_Cygwin|elibc\_Darwin|elibc\_DragonFly|elibc\_FreeBSD|elibc\_HPUX|elibc\_Interix|elibc\_NetBSD|elibc\_OpenBSD|elibc\_SunOS|elibc\_Winnt|elibc\_glibc|elibc\_mintlib|elibc\_musl|elibc\_uclibc|evdev\_gestures|fonts|gold|goma|hardfp|highdpi|hppa|hppa\-hpux|ia64|ia64\-hpux|ia64\-linux|internal\_gles\_conform|jumbo|kernel\_AIX|kernel\_Darwin|kernel\_FreeBSD|kernel\_HPUX|kernel\_NetBSD|kernel\_OpenBSD|kernel\_SunOS|kernel\_Winnt|kernel\_freemint|kernel\_linux|libcxx|lld|m68k|m68k\-mint|mips|mojo|nacl|neon|nios2|opengl|opengles|ozone\_platform\_caca|ozone\_platform\_cast|ozone\_platform\_default\_caca|ozone\_platform\_default\_cast|ozone\_platform\_default\_egltest|ozone\_platform\_default\_gbm|ozone\_platform\_default\_test|ozone\_platform\_egltest|ozone\_platform\_gbm|ozone\_platform\_test|ppc|ppc64|ppc64\-linux|ppc\-aix|ppc\-macos|ppc\-openbsd|prefix|prefix\-guest|riscv|runhooks|s390|sh|smbprovider|sparc|sparc64\-freebsd|sparc64\-solaris|sparc\-fbsd|sparc\-solaris|thinlto|userland\_BSD|userland\_GNU|v4l2\_codec|v4lplugin|vaapi|verbose|vtable\_verify|x64\-cygwin|x64\-freebsd|x64\-macos|x64\-openbsd|x64\-solaris|x86|x86\-cygwin|x86\-fbsd|x86\-freebsd|x86\-interix|x86\-linux|x86\-macos|x86\-netbsd|x86\-openbsd|x86\-solaris|x86\-winnt|xkbcommon)$ while when running the same on the DUT during binary package installation, the contents of $PORTAGE_IUSE are: ^(accessibility|afdo\_chrome\_exp1|afdo\_chrome\_exp2|afdo\_use|app\_shell|asan|authpolicy|autotest|build\_native\_assistant|build\_tests|buildcheck|cfi|chrome\_debug|chrome\_debug\_tests|chrome\_internal|chrome\_media|chrome\_remoting|clang|clang\_tidy|component\_build|cups|debug\_fission|evdev\_gestures|fonts|gold|goma|hardfp|highdpi|internal\_gles\_conform|jumbo|libcxx|lld|mojo|nacl|neon|opengl|opengles|ozone\_platform\_caca|ozone\_platform\_cast|ozone\_platform\_default\_caca|ozone\_platform\_default\_cast|ozone\_platform\_default\_egltest|ozone\_platform\_default\_gbm|ozone\_platform\_default\_test|ozone\_platform\_egltest|ozone\_platform\_gbm|ozone\_platform\_test|runhooks|smbprovider|thinlto|v4l2\_codec|v4lplugin|vaapi|verbose|vtable\_verify|xkbcommon)$ So for some reason the arch flags are missing on the device.
,
Apr 25 2018
Some further info: In _calc_iuse_effective in third_party/portage_tool/pym/portage/package/ebuild/config.py, the IUSE_IMPLICIT (and all associated vars like USE_EXPAND_IMPLICIT, USE_EXPAND_UNPREFIXED, USE_EXPAND) are populated when we emerge the package on through cros_workon_make. However, when it comes to cros deploy (and so on-DUT emerging of the binary package), those environment variables are empty at that time. Is the problem that the variables aren't set, or is that we shouldn't be calling _calc_iuse_effective in this situation?
,
May 11 2018
,
May 15 2018
,
May 21 2018
,
May 25 2018
,
Sep 21
,
Oct 10
,
Oct 10
while this is a bug we should fix, i wonder why you're using `cros deploy` for chromeos-chrome in the first place. if people want custom builds of Chrome, they should be following the simple chrome workflow normally.
,
Oct 11
Hi vapier, By 'simple chrome workflow', are you referring to https://chromium.googlesource.com/chromiumos/docs/+/master/simple_chrome_workflow.md#Using-deploy_chrome ? I don't remember seeing this section when we got started on our workflow 2 years ago. I recall trying to follow this, but we couldn't get it to work with board-specific builds, as non-Googlers. I guess we need to try again, and follow the https://chromium.googlesource.com/chromiumos/docs/+/master/simple_chrome_workflow.md#Using-a-custom-Chrome-OS-build section as well?
,
Oct 12
i've fairly certain our simple chrome workflow has always had a deploy chrome helper, certainly longer than 2 years ago. deploy_chrome was first added to chromite in 2012. deploy_chrome does not, by design, have anything Google-specific in it. it only needs ssh access to a device to work. we don't test `cros deploy chromeos-chrome` anywhere. we do test deploy_chrome heavily.
,
Dec 27
,
Jan 3
assuming resolved with the profile changes we made. if people are still seeing this with ToT, please reopen with new logs. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by stephen....@arm.com
, Apr 24 2018