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

Issue 804513 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Jan 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug



Sign in to add a comment

eve-paladin failed to rebuild previously removed factory-board ebuild

Project Member Reported by bmgordon@chromium.org, Jan 22 2018

Issue description

http://crrev.com/i/551123 removed the factory-board ebuild.  Today, http://crrev.com/c/770257 introduced an unrelated change to vboot_reference.  factory-board depends on vboot_reference, so eve-paladin decided to rebuild it.  Since it was no longer there, the build failed with error "chromeos-base/factory-board-1.0.0-r9::eve-private (masked by: need to rebuild from source)".

This looks like another instance of https://crbug.com/804406, where stale stuff is left over in the chroot.

https://luci-milo.appspot.com/buildbot/chromeos/eve-paladin/2183
 
Cc: bmgordon@chromium.org
The next run created a new chroot and failed with the same error.  Checking to see why a fresh chroot still contains the removed package.
Cc: vapier@chromium.org
Cc: reinauer@chromium.org
Labels: -Pri-2 Pri-0
Bumping priority, since this is apparently blocking commits to vboot_reference.

Can we just revert http://crrev.com/i/551123 while we solve the underlying problem?

Comment 5 by vapier@chromium.org, Jan 23 2018

this is WAI from the packaging side, more or less.  if you want to purge the package, you can add a chroot hook script to remove it everywhere.  look at src/scripts/chroot_version_hooks.d/135_clean_linux-3.4 as an example.
Re #5: Shouldn't a fresh chroot not contain the removed package, though?  I just created a new chroot on my workstation and factory-board wasn't there.

Comment 7 by vapier@chromium.org, Jan 23 2018

yes, a new chroot (or really blowing /build/$BOARD away) would not re-install the package.  but most paladins (by design) don't do either of those things.
Labels: mp-triage
Status: Untriaged (was: Unconfirmed)
This build seems to have started from a fresh chroot, but then it failed with the factory-board references: https://luci-milo.appspot.com/buildbot/chromeos/eve-paladin/2184 .  Am I missing something there?
Owner: hungte@chromium.org
hungte@, could you take a look and see if you missed a step when removing factory-board?  
Status: Started (was: Untriaged)
Re#5 We may need to do this often and I'm not sure if that will mess up chroot version....?

I'm planning to add a dummy ebuild to help existing chroot devices to empty the dependency between factory-board and vboot_reference. Then in the future after most paladins have been updated, we can remove the dummy one.


1) I see the same issue with the local build. Note that I have vboot_reference along with a few other packages in my cros_workon list. Going through repo sync, deleting /build/eve, recreating chroot didn't help.
2) The workaround from #12 works (still building, but got past that point, so no surprises).
Project Member

Comment 14 by bugdroid1@chromium.org, Jan 23 2018

Status: Fixed (was: Started)
CL merged. Let me know if you see more problems.
Thanks for the quick fix!
Status: Verified (was: Fixed)
The next eve-paladin run passed BuildPackages with the original vboot change: https://luci-milo.appspot.com/buildbot/chromeos/eve-paladin/2190

Sign in to add a comment