Add full log for R73-11446.

which is flashed by
  cros flash ssh://dut xbuddy://remote/soraka/R73-11446.0.0/test

Deleted: R73-11446.log 199 KB

R73-11446.log 199 KB View Download

I will see if I can reproduce this.

I started with a clean build root and was able to reproduce the problem. Those messages may not be the root cause though. I am still looking into it.

I can confirm that emerge on the device is expecting the ARCH environment variable, and when it is set cros deploy works properly. I am looking into the best place to put a fix.

NVM the other issue is related but different. We probably want this (from  crbug.com/312041 #3) though:

echo /etc/portage/make.profile > /usr/local/etc/portage/make.profile/parent

You can work around this problem for now by running the following command on the test device:
sudo sh -c 'mount -o remount,rw / && echo /etc/portage/make.profile > /usr/local/etc/portage/make.profile/parent'

If we go with the gmerge fix in:
https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/1390402
cros deploy will be broken for any affected images, and will require flashing an image that includes the fix or using the work around.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/59841abd2f406633cab5e37ad69b30e490fae409

commit 59841abd2f406633cab5e37ad69b30e490fae409
Author: Allen Webb <allenwebb@google.com>
Date: Sat Dec 29 00:14:03 2018

gmerge: Inherit portage profile from /etc/.

After the portage upgrade to 2.3.49, emerge expected ARCH to be set
which is included in /etc/portage/make.profile/make.defaults. This
sets the system profile as the parent so that ARCH is set (along with
the other typical vars).

BUG= chromium:917683 
TEST=cros deploy --board ${BOARD} <test_host> <package>

Change-Id: I7d729160cb6177ffc547fd1c1c6b580dd459e986
Reviewed-on: https://chromium-review.googlesource.com/1390402
Commit-Ready: Allen Webb <allenwebb@google.com>
Tested-by: Allen Webb <allenwebb@google.com>
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/59841abd2f406633cab5e37ad69b30e490fae409/chromeos-base/gmerge/gmerge-9999.ebuild
[add] https://crrev.com/59841abd2f406633cab5e37ad69b30e490fae409/chromeos-base/gmerge/files/parent

Still experiencing issues at ToT.  Posted fix does not seem to help.  (Possibly a different issue, yet deploy still is not functional)

Captured stderr was:
18:16:43: INFO: RunCommand: strip_package --sysroot /build/gale chromeos-base/ap-daemons-9999
18:16:44: DEBUG: RunCommand: ssh -p 22 '-oConnectionAttempts=4' '-oUserKnownHostsFile=/dev/null' '-oProtocol=2' '-oConnectTimeout=30' '-oServerAliveCountMax=3' '-oStrictHostKeyChecking=no' '-oServerAliveInter
val=10' '-oNumberOfPasswordPrompts=0' '-oIdentitiesOnly=yes' -i /tmp/ssh-tmpG46AFQ/testing_rsa root@192.168.82.1 -- mkdir -p /usr/local/tmp/cros-deploy '&&' mktemp -d '--tmpdir=/usr/local/tmp/cros-deploy'
18:16:44: DEBUG: The temporary working directory on the device is /usr/local/tmp/cros-deploy/tmp.whNn3lrEj9
18:16:44: DEBUG: RunCommand: ssh -p 22 '-oConnectionAttempts=4' '-oUserKnownHostsFile=/dev/null' '-oProtocol=2' '-oConnectTimeout=30' '-oServerAliveCountMax=3' '-oStrictHostKeyChecking=no' '-oServerAliveInter
val=10' '-oNumberOfPasswordPrompts=0' '-oIdentitiesOnly=yes' -i /tmp/ssh-tmpG46AFQ/testing_rsa root@192.168.82.1 -- rm -rf /usr/local/tmp/cros-deploy/tmp.whNn3lrEj9/packages/chromeos-base /usr/local/tmp/cros-
deploy/tmp.whNn3lrEj9/portage-tmp '&&' mkdir -p /usr/local/tmp/cros-deploy/tmp.whNn3lrEj9/packages/chromeos-base /usr/local/tmp/cros-deploy/tmp.whNn3lrEj9/portage-tmp
18:16:45: NOTICE: Copying ap-daemons-9999.tbz2 to device.
18:16:45: INFO: [mode:rsync] copy: /build/gale/stripped-packages/chromeos-base/ap-daemons-9999.tbz2 -> 192.168.82.1:/usr/local/tmp/cros-deploy/tmp.whNn3lrEj9/packages/chromeos-base
18:16:45: DEBUG: RunCommand: ssh -p 22 '-oConnectionAttempts=4' '-oUserKnownHostsFile=/dev/null' '-oProtocol=2' '-oConnectTimeout=30' '-oServerAliveCountMax=3' '-oStrictHostKeyChecking=no' '-oServerAliveInter
val=10' '-oNumberOfPasswordPrompts=0' '-oIdentitiesOnly=yes' -i /tmp/ssh-tmpG46AFQ/testing_rsa root@192.168.82.1 -- 'PATH=/usr/local/bin:/usr/local/sbin:$PATH rsync' --version
18:16:45: INFO: Using rsync compression: True
Warning: Permanently added '192.168.82.1' (ED25519) to the list of known hosts.
18:16:47: INFO: Use portage temp dir /usr/local/tmp/cros-deploy/tmp.whNn3lrEj9/portage-tmp
18:16:47: NOTICE: Installing ap-daemons-9999.tbz2.
18:16:47: INFO: RunCommand: ssh -p 22 '-oConnectionAttempts=4' '-oUserKnownHostsFile=/dev/null' '-oProtocol=2' '-oConnectTimeout=30' '-oServerAliveCountMax=3' '-oStrictHostKeyChecking=no' '-oServerAliveInterv
al=10' '-oNumberOfPasswordPrompts=0' '-oIdentitiesOnly=yes' -i /tmp/ssh-tmpG46AFQ/testing_rsa root@192.168.82.1 -- 'FEATURES=-sandbox' 'PORTAGE_CONFIGROOT=/usr/local' "CONFIG_PROTECT='-*'" 'PKGDIR=/usr/local/
tmp/cros-deploy/tmp.whNn3lrEj9/packages' 'PORTDIR=/usr/local/tmp/cros-deploy/tmp.whNn3lrEj9' 'PORTAGE_TMPDIR=/usr/local/tmp/cros-deploy/tmp.whNn3lrEj9/portage-tmp' emerge --usepkg /usr/local/tmp/cros-deploy/t
mp.whNn3lrEj9/packages/chromeos-base/ap-daemons-9999.tbz2 '--root=/'
Warning: Permanently added '192.168.82.1' (ED25519) to the list of known hosts.
!!! Unable to parse profile: '/usr/local/etc/portage/make.profile'
!!! ParseError: Parent '/etc/portage/make.profile' not found: '/usr/local/etc/portage/make.profile/parent'


!!! /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.whNn3lrEj9/profiles/
!!! (You can safely ignore this message when syncing. It's harmless.)


!!! Problem with sandbox binary. Disabling...

!!! Your current profile is invalid. If you have just changed your profile
!!! configuration, you should revert back to the previous configuration.
!!! Allowed actions are limited to --help, --info, --search, --sync, and
!!! --version.

you're describing a jetstream-specific bug which is being tracked in  issue 919594