It's been failing for a while, which is blocking LKGM roll on chromium bots because it depends on the external chrome-sdk package, which are built by -full builders. vaiper@ can you look into this? Here is what jclinton@ thinks (from cros-oncall)


from cros-oncall:
jclinton@ :
looking at bit more at the -full builder failure, we think that maybe chromeos-initramfs failed due to Portage sandbox violation



-Full Builders:
https://cros-goldeneye.corp.google.com/chromeos/legoland/builderSummary?builderGroups=full&limit=100&buildBranch=master

Log:
https://luci-logdog.appspot.com/logs/chromeos/buildbucket/cr-buildbucket.appspot.com/8927508717292208240/+/steps/Archive/0/stdout


11:22:23: ERROR: <class 'chromite.lib.failures_lib.BuildScriptFailure'>: ./mod_image_for_recovery.sh failed (code=1)
Traceback (most recent call last):



- LKGM roll failure on chromeos-daisy-rel
https://ci.chromium.org/p/chromium/builders/luci.chromium.try/chromeos-daisy-rel/146457

Log:
________ running 'src/third_party/chromite/bin/cros chrome-sdk --nogoma --use-external-config --nogn-gen --board=daisy --cache-dir=src/build/cros_cache/ --log-level=error exit' in '/b/swarming/w/ir/cache/builder'
12:10:13: ERROR: cros chrome-sdk failed before completing.
12:10:13: ERROR: Cannot find SDK for 'daisy' with version 11379.0.0
12:10:13: ERROR: (Re-run with --debug for more details.)