Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Starred by 3 users
Status: Verified
Owner:
Closed: Dec 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug



Sign in to add a comment
InitSDK failing everywhere on "chromeos-fonts": temp/environment: line 479: 25096 Segmentation fault
Project Member Reported by diand...@chromium.org, Dec 20 2016 Back to list
Seeing this everywhere.  Trybots.  CQ.  Something is broken badly.

An example:
  https://uberchromegw.corp.google.com/i/chromeos/builders/butterfly-paladin/builds/20958/steps/InitSDK/logs/stdio

Started chromeos-base/chromeos-fonts-0.0.1-r24 (logged in /tmp/chromeos-fonts-0.0.1-r24-Q345vC)
=== Start output for job chromeos-fonts-0.0.1-r24 (0m2.5s) ===
chromeos-fonts-0.0.1-r24: >>> Emerging (1 of 1) chromeos-base/chromeos-fonts-0.0.1-r24::chromiumos
chromeos-fonts-0.0.1-r24:  * Running stacked hooks for pre_pkg_setup
chromeos-fonts-0.0.1-r24:  *    sysroot_build_bin_dir ...
chromeos-fonts-0.0.1-r24:  [ ok ]
chromeos-fonts-0.0.1-r24:  * Running stacked hooks for pre_src_unpack
chromeos-fonts-0.0.1-r24:  *    python_multilib_setup ...
chromeos-fonts-0.0.1-r24:  [ ok ]
chromeos-fonts-0.0.1-r24: >>> Unpacking source...
chromeos-fonts-0.0.1-r24: >>> Source unpacked in /var/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r24/work
chromeos-fonts-0.0.1-r24:  * Running stacked hooks for post_src_unpack
chromeos-fonts-0.0.1-r24:  *    asan_init ...
chromeos-fonts-0.0.1-r24:  [ ok ]
chromeos-fonts-0.0.1-r24: >>> Preparing source in /var/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r24/work ...
chromeos-fonts-0.0.1-r24: >>> Source prepared.
chromeos-fonts-0.0.1-r24: >>> Configuring source in /var/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r24/work ...
chromeos-fonts-0.0.1-r24: >>> Source configured.
chromeos-fonts-0.0.1-r24: >>> Compiling source in /var/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r24/work ...
chromeos-fonts-0.0.1-r24: >>> Source compiled.
chromeos-fonts-0.0.1-r24: >>> Test phase [not enabled]: chromeos-base/chromeos-fonts-0.0.1-r24
chromeos-fonts-0.0.1-r24: 
chromeos-fonts-0.0.1-r24: >>> Install chromeos-fonts-0.0.1-r24 into /var/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r24/image/ category chromeos-base
chromeos-fonts-0.0.1-r24: >>> Completed installing chromeos-fonts-0.0.1-r24 into /var/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r24/image/
chromeos-fonts-0.0.1-r24: 
chromeos-fonts-0.0.1-r24:  * Removing /usr/lib*/*.la
chromeos-fonts-0.0.1-r24:  * Removing /etc/init.d
chromeos-fonts-0.0.1-r24:  * Removing /etc/conf.d
chromeos-fonts-0.0.1-r24:  * Removing /etc/logrotate.d
chromeos-fonts-0.0.1-r24: ./
chromeos-fonts-0.0.1-r24: >>> Done.
chromeos-fonts-0.0.1-r24: >>> Installing (1 of 1) chromeos-base/chromeos-fonts-0.0.1-r24::chromiumos
chromeos-fonts-0.0.1-r24:  * Removing /usr/lib*/*.la
chromeos-fonts-0.0.1-r24:  * Removing /etc/init.d
chromeos-fonts-0.0.1-r24:  * Removing /etc/conf.d
chromeos-fonts-0.0.1-r24:  * Removing /etc/logrotate.d
chromeos-fonts-0.0.1-r24: /var/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r24/temp/environment: line 479: 25096 Segmentation fault      "$@"
chromeos-fonts-0.0.1-r24:  * ERROR: chromeos-base/chromeos-fonts-0.0.1-r24::chromiumos failed (preinst phase):
chromeos-fonts-0.0.1-r24:  *   (no error message)
chromeos-fonts-0.0.1-r24:  * 
chromeos-fonts-0.0.1-r24:  * Call stack:
chromeos-fonts-0.0.1-r24:  *     ebuild.sh, line  93:  Called pkg_preinst
chromeos-fonts-0.0.1-r24:  *   environment, line 388:  Called generate_font_cache
chromeos-fonts-0.0.1-r24:  *   environment, line 360:  Called qemu_run '/usr/bin/fc-cache' '-f' '-v'
chromeos-fonts-0.0.1-r24:  *   environment, line 502:  Called die
chromeos-fonts-0.0.1-r24:  * The specific snippet of code:
chromeos-fonts-0.0.1-r24:  *           "$@" || die;
chromeos-fonts-0.0.1-r24:  * 
chromeos-fonts-0.0.1-r24:  * If you need support, post the output of `emerge --info '=chromeos-base/chromeos-fonts-0.0.1-r24::chromiumos'`,
chromeos-fonts-0.0.1-r24:  * the complete build log and the output of `emerge -pqv '=chromeos-base/chromeos-fonts-0.0.1-r24::chromiumos'`.
chromeos-fonts-0.0.1-r24:  * The complete build log is located at '/var/log/portage/chromeos-base:chromeos-fonts-0.0.1-r24:20161220-152827.log'.
chromeos-fonts-0.0.1-r24:  * For convenience, a symlink to the build log is located at '/var/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r24/temp/build.log'.
chromeos-fonts-0.0.1-r24:  * The ebuild environment file is located at '/var/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r24/temp/environment'.
chromeos-fonts-0.0.1-r24:  * Working directory: '/usr/lib64/portage/pym'
chromeos-fonts-0.0.1-r24:  * S: '/var/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r24/work/chromeos-fonts-0.0.1'
chromeos-fonts-0.0.1-r24: !!! FAILED preinst: 1
chromeos-fonts-0.0.1-r24: >>> Failed to install chromeos-base/chromeos-fonts-0.0.1-r24, Log file:
chromeos-fonts-0.0.1-r24: >>>  '/var/log/portage/chromeos-base:chromeos-fonts-0.0.1-r24:20161220-152827.log'
chromeos-fonts-0.0.1-r24: 
chromeos-fonts-0.0.1-r24:  * Messages for package chromeos-base/chromeos-fonts-0.0.1-r24:
chromeos-fonts-0.0.1-r24: 
chromeos-fonts-0.0.1-r24:  * ERROR: chromeos-base/chromeos-fonts-0.0.1-r24::chromiumos failed (preinst phase):
chromeos-fonts-0.0.1-r24:  *   (no error message)
chromeos-fonts-0.0.1-r24:  * 
chromeos-fonts-0.0.1-r24:  * Call stack:
chromeos-fonts-0.0.1-r24:  *     ebuild.sh, line  93:  Called pkg_preinst
chromeos-fonts-0.0.1-r24:  *   environment, line 388:  Called generate_font_cache
chromeos-fonts-0.0.1-r24:  *   environment, line 360:  Called qemu_run '/usr/bin/fc-cache' '-f' '-v'
chromeos-fonts-0.0.1-r24:  *   environment, line 502:  Called die
chromeos-fonts-0.0.1-r24:  * The specific snippet of code:
chromeos-fonts-0.0.1-r24:  *           "$@" || die;
chromeos-fonts-0.0.1-r24:  * 
chromeos-fonts-0.0.1-r24:  * If you need support, post the output of `emerge --info '=chromeos-base/chromeos-fonts-0.0.1-r24::chromiumos'`,
chromeos-fonts-0.0.1-r24:  * the complete build log and the output of `emerge -pqv '=chromeos-base/chromeos-fonts-0.0.1-r24::chromiumos'`.
chromeos-fonts-0.0.1-r24:  * The complete build log is located at '/var/log/portage/chromeos-base:chromeos-fonts-0.0.1-r24:20161220-152827.log'.
chromeos-fonts-0.0.1-r24:  * For convenience, a symlink to the build log is located at '/var/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r24/temp/build.log'.
chromeos-fonts-0.0.1-r24:  * The ebuild environment file is located at '/var/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r24/temp/environment'.
chromeos-fonts-0.0.1-r24:  * Working directory: '/usr/lib64/portage/pym'
chromeos-fonts-0.0.1-r24:  * S: '/var/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r24/work/chromeos-fonts-0.0.1'
=== Complete: job chromeos-fonts-0.0.1-r24 (0m2.5s) ===
Failed chromeos-base/chromeos-fonts-0.0.1-r24 (in 0m2.5s). Your build has failed.

 
Cc: akes...@chromium.org diand...@chromium.org
 Issue 676008  has been merged into this issue.
Similar old bug is  bug #667506 
Failures seen so far:
* https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/13158
  - daisy_spring-paladin
  - butterfly-paladin
  - lumpy-paladin
* PCQ of https://chromium-review.googlesource.com/#/c/422416/
  - binhost-pre-cq
  - mixed-b-pre-cq
  - mixed-c-pre-cq
  - mixed-a-pre-cq
Comment 4 by sbasi@chromium.org, Dec 20 2016
Vapier pinged me saying:

"toolchain upgrade could cause that.  ping luis/yunlian." As they are already cc-ed, let's see what they say.
In fact, everything since this morning here:

https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/compile_only_pre_cq/

Last success was: Tue, 2016-12-20 2:38:46 AM
First fail was:   Tue, 2016-12-20 7:10:36 AM


I'm definitely far out of scope here.  Any help is appreciated.  I'll keep stumbling around in the dark, though.
Cc: jdufault@chromium.org
The fc-cache causes segmentation faults even outside qemu. I will try to upgrade fontconfig to see whether that helps.
Owner: yunlian@chromium.org
Status: Assigned
Via IM, I see Yunlian saying "OK, I can take a look".  Assigning owner based on this.

Luis says "we migrated glibc", so that is postulated to be the root cause here.
this matches the gblic migration. 

the glibc migration is validated by a special builder called chromiumos-sdk builder. This builder finished 

the chromiumos-sdk was succesful at Tue Dec 20 05:28:43 2016
which matches the timing for 
Last success was: Tue, 2016-12-20 2:38:46 AM
First fail was:   Tue, 2016-12-20 7:10:36 AM

we dont understand why the special builder or the testing did not catch this.
so, we are going to revert the CL and continue investigating.


@9: after the revert, I assume you can do something to expedite making this take effect so we don't need to wait for the chromiumos-sdk builder to run again?
Project Member Comment 11 by bugdroid1@chromium.org, Dec 20 2016
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8

commit 2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8
Author: Yunlian Jiang <yunlian@chromium.org>
Date: Tue Dec 20 18:49:07 2016

Revert "glibc: roll to 2.23"

New glibc causes segmentation fault on fc-cache. We need
to revert this first.

This reverts commit 88ad3013d1add4b162d277fbacf9b491fc00ad4e.

BUG= 676013 
TEST=sudo emerge chromeos-fonts passes with old glibc.

Change-Id: I932e3ccc4ab71da756c4d47aff1a6fa4e4acf490
Reviewed-on: https://chromium-review.googlesource.com/422417
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Commit-Queue: Yunlian Jiang <yunlian@chromium.org>
Tested-by: Yunlian Jiang <yunlian@chromium.org>

[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/eblits/common.eblit
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/eblits/src_unpack.eblit
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/2.19/glibc-2.19-ia64-gcc-4.8-reloc-hack.patch
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/2.17/glibc-2.17-hardened-pie.patch
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/eblits/pkg_postinst.eblit
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/local/glibc-2.19-CVE-2015-7547.patch
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/glibc-2.23-r3.ebuild
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/eblits/pkg_pretend.eblit
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/eblits/pkg_setup.eblit
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/eblits/src_compile.eblit
[rename] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/local/glibc-2.19-clang-fortify.patch
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/Manifest
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/metadata.xml
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/nscd.service
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/local/glibc-2.19-ldso-pie.patch
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/2.18/glibc-2.18-hardened-inittls-nosysenter.patch
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/local/glibc-2.19-CVE-2014-7817.patch
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/eblits/src_prepare.eblit
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/eblits/pkg_preinst.eblit
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/nscd.tmpfilesd
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/eblits/src_test.eblit
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/2.19/glibc-2.19-hardened-configure-picdefault.patch
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/nscd
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/local/glibc-2.19-CVE-2013-7423.patch
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/local/glibc-2.19-CVE-2015-1472.patch
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/local/glibc-2.23-file-mangle.patch
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/local/glibc-2.21-resize-dtv.patch
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/local/glibc-2.19-file-mangle.patch
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/local/glibc-2.23-fortify-warning.patch
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/local/glibc-2.23-set-ld.patch
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/eblits/src_install.eblit
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/2.20/glibc-2.20-gentoo-chk_fail.c
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/eblits/src_configure.eblit
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/glibc-2.19-r13.ebuild
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/nsswitch.conf

Project Member Comment 12 by bugdroid1@chromium.org, Dec 20 2016
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8

commit 2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8
Author: Yunlian Jiang <yunlian@chromium.org>
Date: Tue Dec 20 18:49:07 2016

Revert "glibc: roll to 2.23"

New glibc causes segmentation fault on fc-cache. We need
to revert this first.

This reverts commit 88ad3013d1add4b162d277fbacf9b491fc00ad4e.

BUG= 676013 
TEST=sudo emerge chromeos-fonts passes with old glibc.

Change-Id: I932e3ccc4ab71da756c4d47aff1a6fa4e4acf490
Reviewed-on: https://chromium-review.googlesource.com/422417
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Commit-Queue: Yunlian Jiang <yunlian@chromium.org>
Tested-by: Yunlian Jiang <yunlian@chromium.org>

[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/eblits/common.eblit
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/eblits/src_unpack.eblit
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/2.19/glibc-2.19-ia64-gcc-4.8-reloc-hack.patch
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/2.17/glibc-2.17-hardened-pie.patch
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/eblits/pkg_postinst.eblit
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/local/glibc-2.19-CVE-2015-7547.patch
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/glibc-2.23-r3.ebuild
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/eblits/pkg_pretend.eblit
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/eblits/pkg_setup.eblit
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/eblits/src_compile.eblit
[rename] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/local/glibc-2.19-clang-fortify.patch
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/Manifest
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/metadata.xml
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/nscd.service
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/local/glibc-2.19-ldso-pie.patch
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/2.18/glibc-2.18-hardened-inittls-nosysenter.patch
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/local/glibc-2.19-CVE-2014-7817.patch
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/eblits/src_prepare.eblit
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/eblits/pkg_preinst.eblit
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/nscd.tmpfilesd
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/eblits/src_test.eblit
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/2.19/glibc-2.19-hardened-configure-picdefault.patch
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/nscd
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/local/glibc-2.19-CVE-2013-7423.patch
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/local/glibc-2.19-CVE-2015-1472.patch
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/local/glibc-2.23-file-mangle.patch
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/local/glibc-2.21-resize-dtv.patch
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/local/glibc-2.19-file-mangle.patch
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/local/glibc-2.23-fortify-warning.patch
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/local/glibc-2.23-set-ld.patch
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/eblits/src_install.eblit
[modify] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/files/2.20/glibc-2.20-gentoo-chk_fail.c
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/eblits/src_configure.eblit
[add] https://crrev.com/2bb782d9bdb58161673a4bc8b3d8e6596a1daaf8/sys-libs/glibc/glibc-2.19-r13.ebuild
[delete] https://crrev.com/ac142141fa6b60b2463e26ca53272ac1d1b3a996/sys-libs/glibc/files/nsswitch.conf

we just did the revert and chump'ed it. 
however, that is not enough. we need to follow the instructions here:

https://sites.google.com/a/google.com/chromeos/for-team-members/infrastructure/chromeos-admin/reverting-toolchain-rolls


Project Member Comment 14 by bugdroid1@chromium.org, Dec 20 2016
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/dcbaa9fa1bb7ef149465444ab17a4485cc596daa

commit dcbaa9fa1bb7ef149465444ab17a4485cc596daa
Author: Yunlian Jiang <yunlian@google.com>
Date: Tue Dec 20 19:15:04 2016

Choose an older FULL_BINHOST to revert glibc changes.

This revert glibc-2.23 upgrades in sdk.

BUG= chromium:676013 
TEST=The BINHOST contains glibc 2.19 instead of 2.23

Change-Id: I0726e7ddd97ce06a1823757ad1025139950ab155
Reviewed-on: https://chromium-review.googlesource.com/422649
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Yunlian Jiang <yunlian@chromium.org>
Tested-by: Yunlian Jiang <yunlian@chromium.org>

[modify] https://crrev.com/dcbaa9fa1bb7ef149465444ab17a4485cc596daa/chromeos/config/make.conf.amd64-host

My naive reading of the instructions indicates that we also need to roll sdk_version.conf back.  The above CL doesn't do that.

Can someone indicate if it was skipped on purpose or on accident?
My naive reading of the instructions also indicates that we should choose to stop the build at <https://uberchromegw.corp.google.com/i/chromiumos/builders/chromiumos-sdk/builds/7622>.  Can someone help confirm?
Project Member Comment 17 by bugdroid1@chromium.org, Dec 20 2016
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/32b77d6f96c24560e018b61ecc35dd112d0997e2

commit 32b77d6f96c24560e018b61ecc35dd112d0997e2
Author: Yunlian Jiang <yunlian@google.com>
Date: Tue Dec 20 19:43:05 2016

Use old sdk_version to revert glibc upgrade.

This uses old sdk_version to revert glibc upgrade.

BUG= chromium:676013 
TEST=The old sdk contains glibc 2.19 instead of glibc 2.23.

Change-Id: I380ee32f34fe612178852cfc1536a38a28ea4ece
Reviewed-on: https://chromium-review.googlesource.com/422393
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Yunlian Jiang <yunlian@chromium.org>
Tested-by: Yunlian Jiang <yunlian@chromium.org>

[modify] https://crrev.com/32b77d6f96c24560e018b61ecc35dd112d0997e2/chromeos/binhost/host/sdk_version.conf

Status: Fixed
I see some PCQ passes.  Marking as Fixed.
 Issue 676160  has been merged into this issue.
Comment 20 by dchan@google.com, Mar 4 2017
Labels: VerifyIn-58
Status: Verified
Sign in to add a comment