New issue
Advanced search Search tips

Issue 861924 link

Starred by 2 users
Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Task
Build-Toolchain



Sign in to add a comment

Update chromiumos-sdk bootstrap to use a newer stage3 chromium os sdk tarball

Project Member Reported by manojgupta@chromium.org, Jul 9 
Currently chromiumos-sdk builder does the bootstrapping using an ancient stage3 Gentoo tarball from 2014. This should be replaced by a newer stage3, preferably using the chroimum os's stable SDK tarball itself.
This will fix several issues:

1. Portage supports EAPI=6 but when chromiumos-sdk builder is bootstrapping portage, any dependencies still need to be EAPI=5. This has caused several breakages in past.
2. Many times packages fail to build on the SDK builder because of missing dependencies. But this is difficult to triage on regular chroots since user chroot may already have the correct dependencies.
3. Will reduce the time spent in InitSDK stage since there will be a smaller list of packages that need to be built.
4. Won't have to depend on what Gentoo publishes in its own stage3 tarballs.

Comment 1 by vapier@chromium.org, Jul 9

Components: -Infra>Client>ChromeOS>CI Infra>Client>ChromeOS>Build
i've cached a newerish stage3 here:
  gs://chromiumos-sdk/stage3-amd64-2017.02.09.tar.xz

but in reality, because of the toolchain team's decision to not upgrade gcc, we will never be able to upgrade to anything newer than that.  Gentoo has moved on to gcc-7 at this point.

Comment 2 by manojgupta@chromium.org, Jul 9 

My thinking is to use a stable cros chroot as the stage3 instead of using the one from Gentoo. 

A test tryjob is here that uses 2018.07.08.081901 SDK:
https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8941451116011203264

Wdyt?

Comment 3 by vapier@chromium.org, Jul 9 

if the toolchain team continues holding back gcc, then i don't think we'll have a choice but to design a new system that uses an older existing CrOS SDK to bootstrap itself.  but that'll def require a design doc to pull off as there's a lot of moving pieces.

Comment 4 by la...@chromium.org, Jul 13

Labels: -Type-Bug Type-Task
Status: Available (was: Untriaged)

Comment 5 by nedngu...@google.com, Jan 11 

#3: Mike, why do you think we need the older existing CrOS SDK to do the bootstrap?

What would break if we switch chromiumos-sdk builder to use latest SDK (the same one used by CQ builders)?

Comment 6 by nedngu...@google.com, Jan 11 

NVM, I found your doc on this bug: https://docs.google.com/document/d/1LXsUw21yieX91_J2MrREiKRfs-fU7kA0xXm_tao53IY/edit?ts=5c37be59#

Will read the doc & comment directly on it if I have more questions
►

Sign in to add a comment