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

Issue 914032 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Dec 12
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

buddy, peach-pit failed on build_packages

Project Member Reported by kbleicher@google.com, Dec 11

Issue description

buddy and peach-pit failed on the latest M71 Beta Build.. Boards excluded from the build as a result (images not available).

buddy:
Log: https://luci-logdog.appspot.com/logs/chromeos/buildbucket/cr-buildbucket.appspot.com/8927456641422775264/+/steps/BuildPackages__afdo_use_/0/stdout
Fail on BuildPackages [afdo_use]
Failed to emerge chromeos-base/chromeos-chrome-71.0.3578.94_rc-r1 for /build/buddy/, Log file: '/build/buddy/tmp/portage/logs/chromeos-base:chromeos-chrome-71.0.3578.94_rc-r1:20181211-075249.log'
Packages failed in ./build_packages: chromeos-base/chromeos-chrome


peach-pit:
Log: https://luci-logdog.appspot.com/logs/chromeos/buildbucket/cr-buildbucket.appspot.com/8927456591936329616/+/steps/BuildPackages__afdo_use_/0/stdout
Fail on BuildPackages [afdo_use]
Failed to emerge chromeos-base/chromeos-chrome-71.0.3578.94_rc-r1 for /build/peach_pit/, Log file: '/build/peach_pit/tmp/portage/logs/chromeos-base:chromeos-chrome-71.0.3578.94_rc-r1:20181211-081405.log'
Packages failed in ./build_packages: chromeos-base/chromeos-chrome


 
Owner: osh...@chromium.org
This looks like a Chrome failure. @oshima can you take a look please, bounce back to me if it's not.
Status: Started (was: Untriaged)
Owner: athilenius@chromium.org
Status: Assigned (was: Started)
Looks like the bot has unexpected changes in third_party/android_tools ? can you look into the bot?



chromeos-chrome-71.0.3578.94_rc-r1: 
chromeos-chrome-71.0.3578.94_rc-r1: ________ running '/usr/bin/python2.7 src/chromeos/assistant/internal/build_libassistant.py --sync_only' in '/home/chrome-bot/chrome_root/.'
chromeos-chrome-71.0.3578.94_rc-r1: 
chromeos-chrome-71.0.3578.94_rc-r1: third_party/android_tools (ERROR)
chromeos-chrome-71.0.3578.94_rc-r1: ----------------------------------------
chromeos-chrome-71.0.3578.94_rc-r1: [0:00:00] Started.
chromeos-chrome-71.0.3578.94_rc-r1: [0:00:01] _____ third_party/android_tools : Attempting rebase onto 130499e25286f4d56acafa252fee09f3cc595c49...
chromeos-chrome-71.0.3578.94_rc-r1: [0:00:01] 
chromeos-chrome-71.0.3578.94_rc-r1: [0:00:01] Rebase produced error output:
chromeos-chrome-71.0.3578.94_rc-r1: Cannot rebase: Your index contains uncommitted changes.
chromeos-chrome-71.0.3578.94_rc-r1: Please commit or stash them.
chromeos-chrome-71.0.3578.94_rc-r1: ----------------------------------------
chromeos-chrome-71.0.3578.94_rc-r1: Error: 4> Unrecognized error, please merge or rebase manually.
Owner: osh...@chromium.org
chromeos-chrome-71.0.3578.0-r1.ebuild on M71 wasn't updated and this happened on 2 different runs. The failure both times was during the Chrome emerge step, I think this was Chrome related.
Do we need to reassign, etc.?
I onl see one failure on each bot:

https://cros-goldeneye.corp.google.com/chromeos/legoland/builderHistory?buildConfig=buddy-release&buildBranch=release-R71-11151.B
https://cros-goldeneye.corp.google.com/chromeos/legoland/builderHistory?buildConfig=peach_pit-release&buildBranch=release-R71-11151.B

Do you have a link to two different runs?


It looks to me that failrue is due to local git repo state:

> chromeos-chrome-71.0.3578.94_rc-r1: Cannot rebase: Your index contains uncommitted changes.


and I don't think chrome change can cause such error. 
If this was only in one build, can we start next build?

And I'm building them against a stabalize branch, but these hiccups are quite disruptive and create extra work.

Any chance we can identify root causes and improve the framework?  I don't want to just close this out since it's a symptom of a larger problem.

Sign in to add a comment