New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 807587 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jan 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

VMtests failed on Latiku in cloud_FsLayout

Reported by vpalatin@chromium.org, Jan 31 2018

Issue description

the last CQ run failed on all 3 latiku-paladin in the cloud_FsLayout VMTest

e.g. https://luci-milo.appspot.com/buildbot/chromeos/lakitu-paladin/9062

01/31 07:51:43.988 ERROR|    cloud_FsLayout:0079| cmd "find /sbin /bin /usr/sbin ! -type d | sort" failed. Diff: 
['--- \n',
 '+++ \n',
 '@@ -250,6 +250,8 @@\n',
 ' /usr/sbin/rtcwake\n',
 ' /usr/sbin/sshd\n',
 ' /usr/sbin/sysctl\n',
 '+/usr/sbin/update-env\n',
 '+/usr/sbin/update-etc\n',
 ' /usr/sbin/update_engine\n',
 ' /usr/sbin/useradd\n',
 ' /usr/sbin/userdel\n']

Those 2 files /usr/sbin/update-* files are added by sys-apps/portage
I guess it might be related to (ie the portage upgrade and the related fixes for latiku) :
https://chromium-review.googlesource.com/#/c/chromiumos/platform/dev-util/+/889957/
as mentioned in https://chromium-review.googlesource.com/#/c/chromiumos/overlays/chromiumos-overlay/+/815597/

This is just a CQ run, but I think the offender is already submitted ?
(but might solve itself when crrev.com/c/815597 got in ?)
 

Comment 1 by vapier@chromium.org, Jan 31 2018

Owner: vapier@chromium.org
Status: Fixed (was: Untriaged)
the CL that caused the breakage was chumped, but the CL that needed it was merged (CL:815597), so it's sorted itself out

Sign in to add a comment