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

Issue 613594 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug



Sign in to add a comment

simplechrome builders fail to find clock_gettime() (glibc version mismatch?)

Project Member Reported by semenzato@chromium.org, May 20 2016

Issue description

The chrome pfq is red for at least this reason.  Error from this log:

https://uberchromegw.corp.google.com/i/chromeos/builders/x86-alex-chrome-pfq/builds/604/steps/SimpleChromeWorkflow/logs/stdio

FAILED: mksnapshot 
/tmp/cbuildbot-tmpnsvlI1/chrome-sdk-cacheOkJjts/cache/chrome-sdk/tarballs/x86-alex+__b__cbuild__internal_master__buildbot_archive__x86-alex-chrome-pfq__R52-8349.0.0-rc2+target_toolchain/usr/bin/clang++ -Wl,--as-needed -lstdc++ -lm -Wl,-O1 -Wl,-O2 -Wl,--as-needed -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -pthread -Wl,-z,noexecstack -fPIC -fuse-ld=gold -Wl,--disable-new-dtags -fuse-ld=gold -m32 -Wl,-O1 -Wl,--as-needed -Wl,--gc-sections -o mksnapshot -Wl,--start-group obj.host/v8/src/snapshot/mksnapshot.mksnapshot.o obj.host/v8/src/libv8_base.a obj.host/v8/src/libv8_nosnapshot.a obj.host/v8/src/libv8_libplatform.a obj.host/third_party/icu/libicui18n.a obj.host/third_party/icu/libicuuc.a obj.host/v8/src/libv8_libbase.a -Wl,--end-group  -ldl -lrt
/tmp/cbuildbot-tmpnsvlI1/chrome-sdk-cacheOkJjts/cache/chrome-sdk/tarballs/x86-alex+__b__cbuild__internal_master__buildbot_archive__x86-alex-chrome-pfq__R52-8349.0.0-rc2+target_toolchain/usr/bin/../lib/gcc/i686-pc-linux-gnu/4.9.x/libstdc++.so: error: undefined reference to 'clock_gettime', version 'GLIBC_2.17'
clang-3.8: error: linker command failed with exit code 1 (use -v to see invocation)

from this builder:
https://uberchromegw.corp.google.com/i/chromeos/builders/master-chromium-pfq



 
Summary: simplechrome builders fail to find clock_gettime() (glibc version mismatch?) (was: alex and x86-generic simplechrome builders fail to find clock_gettime())
This is also happening on the x86-generic builder on the external waterfall.  Has been happening for two days (since May 18).
Cc: steve...@chromium.org ihf@chromium.org
Which builder exactly? (link?)

On the pfq it started happening at refs/tags/52.0.2740.2. There were also a bunch of chromeos changes. I am attempting to reproduce locally now.

Labels: -Pri-1 ReleaseBlock-Dev M-52 Pri-0
Owner: ihf@chromium.org
Status: Assigned (was: Untriaged)
ihf@ marking this P0 and releaseblock-dev since this is blocking M52 branch.
Cc: josa...@chromium.org gkihumba@chromium.org
I couldn't get this to fail locally, even using gyp.

Since it is failing on a chromium builder also (https://uberchromegw.corp.google.com/i/chromeos/builders/x86-generic-chromium-pfq) I can try a bisect.

Bisect builds are here (starting with 52.0.2740.2 which should fail and 52.0.2740.0 which should pass):
https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/chromium-pfq

Comment 6 by ihf@chromium.org, May 20 2016

I have no repro so far either.
Cc: shenhan@chromium.org llozano@chromium.org
I strongly suspect this CL as the root cause:

https://chromium-review.googlesource.com/#/c/330900/

I see a bunch of compiler warnings that do not exist prior to that CL (not to mention the link failure).

Project Member

Comment 8 by bugdroid1@chromium.org, May 20 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/ab6241b0f6bb4c6c9f3dcaf50f2d0b077036162a

commit ab6241b0f6bb4c6c9f3dcaf50f2d0b077036162a
Author: Han Shen <shenhan@chromium.org>
Date: Fri May 20 22:04:43 2016

Revert "Configure ChromeOS clang for simple-chrome."

This reverts commit a051214394e94423057db168b1c513f90e59e7e9.

BUG= chromium:613594 

Change-Id: I3baec73193fcb62115a5ed30f778055a287c108a
Reviewed-on: https://chromium-review.googlesource.com/346227
Reviewed-by: Luis Lozano <llozano@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Tested-by: Ilja Friedel <ihf@chromium.org>

[modify] https://crrev.com/ab6241b0f6bb4c6c9f3dcaf50f2d0b077036162a/cli/cros/cros_chrome_sdk.py

Seems like this is resolved (e.g. PFQ did not fail with this error after fix landed)


Anything else pending on this one?
Owner: steve...@chromium.org
Status: Fixed (was: Assigned)
Nope, makring fixed.

Project Member

Comment 11 by bugdroid1@chromium.org, May 23 2016

Labels: merge-merged-release-R52-8350.B
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/bcf188194d1f96dc7471e33e06e02aba1f13074b

commit bcf188194d1f96dc7471e33e06e02aba1f13074b
Author: Han Shen <shenhan@chromium.org>
Date: Fri May 20 22:04:43 2016

Revert "Configure ChromeOS clang for simple-chrome."

This reverts commit a051214394e94423057db168b1c513f90e59e7e9.

BUG= chromium:613594 

Change-Id: I3baec73193fcb62115a5ed30f778055a287c108a
Reviewed-on: https://chromium-review.googlesource.com/346227
Reviewed-by: Luis Lozano <llozano@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Tested-by: Ilja Friedel <ihf@chromium.org>
(cherry picked from commit ab6241b0f6bb4c6c9f3dcaf50f2d0b077036162a)
Reviewed-on: https://chromium-review.googlesource.com/346741
Reviewed-by: Luis Lozano <llozano@google.com>
Tested-by: Grace Kihumba <gkihumba@chromium.org>

[modify] https://crrev.com/bcf188194d1f96dc7471e33e06e02aba1f13074b/cli/cros/cros_chrome_sdk.py

Status: Verified (was: Fixed)
closing it please reopen if its not fixed.

Sign in to add a comment