Factory image creation fails on kevin-release. |
||||
Issue description12:36:26: INFO: RunCommand: /b/cbuild/internal_master/chromite/bin/cros_sdk 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmpex5aoV' -- ./make_netboot.sh '--board=kevin' '--image_dir=/mnt/host/source/src/build/images/kevin/R52-8300.0.0-a3' in /b/cbuild/internal_master 12:36:41: ERROR: return code: 1; command: /b/cbuild/internal_master/chromite/bin/cros_sdk 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmpex5aoV' -- ./make_netboot.sh '--board=kevin' '--image_dir=/mnt/host/source/src/build/images/kevin/R52-8300.0.0-a3' !!! CONFIG_PROTECT is empty for '/build/kevin/' ERROR : Mon May 9 12:36:41 PDT 2016 ERROR : PGID PPID PID ELAPSED TIME %CPU COMMAND ERROR : Arguments of 10: ./make_netboot.sh '--board=kevin' '--image_dir=/mnt/host/source/src/build/images/kevin/R52-8300.0.0-a3' ERROR : Backtrace: (most recent call is last) ERROR : make_netboot.sh:69:main(), called: emerge_custom_kernel 'bk_HKr2Pml2' ERROR : common.sh:1250:emerge_custom_kernel(), called: die 'Cannot emerge chromeos-initramfs' ERROR : ERROR : Error was: ERROR : Cannot emerge chromeos-initramfs
,
May 10 2016
Passing to a current sheriff to find an owner.
,
May 10 2016
from what I can see this has never worked: https://uberchromegw.corp.google.com/i/chromeos/builders/kevin-release/ All builds have failed - I assume it's not a problem yet? Giving it to Katie, she can close if it's not an issue
,
May 10 2016
When the release builders were reorganized last Friday, the builders were renamed. That makes history from before the reorg hard to find.
,
May 10 2016
ok -- can you point us to that history?
,
May 10 2016
kevin was in "gru-release-group". I'm having trouble finding the detailed logs. What I can see is that there were 63 builds of that group, and none of them ever passed. I think you're right. This has never worked.
,
May 11 2016
we believe this should go away once we move to chromeos-4.4 kernel - so i'm not sure we're planning on fixing it unless folks have reasons to believe otherwise
,
May 11 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by dgarr...@chromium.org
, May 10 2016