Complete error message for gtest in attachment. I blocked out my ip address. 

Deleted: eve_cros_deploy_error.txt 8.5 KB

eve_cros_deploy_error.txt 8.5 KB View Download

I've seen this failure as well ... and just on eve.

From err log,
bash: emerge: command not found

Seems test images from build server don't currently contain emerge dep while those I've built locally (./build_packages && ./build_image test) do as well as test images for other machines.

On machine w/ emerge I additionally see these portage related dirs,


/usr/local/etc/portage
/usr/local/lib64/python2.7/site-packages/portage
/usr/local/lib/portage
/usr/local/lib/portage/pym/portage
/usr/local/share/portage
/usr/share/dev-install/portage
/usr/share/portage
/etc/portage
/mnt/stateful_partition/dev_image/etc/portage
/mnt/stateful_partition/dev_image/lib64/python2.7/site-packages/portage
/mnt/stateful_partition/dev_image/lib/portage
/mnt/stateful_partition/dev_image/lib/portage/pym/portage
/mnt/stateful_partition/dev_image/share/portage
/mnt/stateful_partition/var_overlay/tmp/portage
/mnt/stateful_partition/var_overlay/lib/portage
/mnt/stateful_partition/var_overlay/log/portage


While an eve w/o emerge has only,

/usr/share/dev-install/portage
/usr/share/portage
/etc/portage

Mounting the test image from the builder for 9211.0.0 I also find emerge in path,

/usr/local/lib/portage/bin/emerge

So its definitely part of the chromiumos_test_image.bin

So a workaround is to run 'test_that' which seems to properly mount stateful

mount | grep /usr/local
/dev/mmcblk0p1 on /usr/local type ext4 (rw,nodev,relatime,seclabel,commit=600,data=ordered)

Not sure if this failure to mount stateful is unique to eve or if something globally has changed.

Still not sure why exactly this is being noticed on eve but even simpler workaround should be to run dev_image locally on cros device.

No longer an issue.