The chromeos-chrome ebuild on veyron_minnie canary throws out lots of errors during the install phase, even though the emerge actually succeeds:

chromeos-chrome-59.0.3041.0_rc-r1: armv7a-cros-linux-gnueabi-strip: '/var/cache/chromeos-chrome/chrome-src-internal/src/out_veyron_minnie/Release/ppapi/examples/video_decode': No such file
<snip>
chromeos-chrome-59.0.3041.0_rc-r1: rsync: link_stat "/home/chrome-bot/chrome_root/src/chrome/test/functional" failed: No such file or directory (2)
<snip>
chromeos-chrome-59.0.3041.0_rc-r1: cp: cannot create hard link '/build/veyron_minnie/tmp/portage/chromeos-base/chromeos-chrome-59.0.3041.0_rc-r1/work/autotest-work/client/deps/chrome_test/README' to 'chrome_test/
<etc>

Log is here:
https://uberchromegw.corp.google.com/i/chromeos/builders/veyron_minnie-release/builds/962/steps/BuildPackages%20%5Bafdo_use%5D/logs/stdio

The samus canary (https://uberchromegw.corp.google.com/i/chromeos/builders/samus-release/builds/4131/steps/BuildPackages%20%5Bafdo_use%5D/logs/stdio) doesn't show the same errors, so it could be ARM-specific, but it could also be that the chromeos-chrome emerge log is not completely dumped to the main log because compilation doesn't take the same amount of time.