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

Issue 596254 link

Starred by 2 users
Status: Verified
Owner: ----
Closed: Apr 2016
Cc:
josephsih@chromium.org
d...@chromium.org
dgreid@chromium.org
vadimsh@chromium.org
█ ttsang@chromium.org
steve...@chromium.org
█ agnescheng@chromium.org
█ bhthompson@chromium.org
chrome-trooper-bugs@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Chrome linker error on Cave canary

Project Member Reported by jwer...@chromium.org, Mar 19 2016 
The glados-release-group canary fails on the Cave board with this weird error:

chromeos-chrome-51.0.2679.0_rc-r1: [4712/24498] ACTION Generating resources from gen/content/browser/tracing/tracing_resources.grd
chromeos-chrome-51.0.2679.0_rc-r1: [4712/24498] LINK mksnapshot
chromeos-chrome-51.0.2679.0_rc-r1: FAILED: x86_64-pc-linux-gnu-g++ -Wl,-O1 -Wl,-O2 -Wl,--as-needed -freorder-functions=callgraph -Wl,-rosegment -Wl,--plugin-opt,split_segment=yes -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -pthread -Wl,-z,noexecstack -fPIC -fuse-ld=gold -Wl,--disable-new-dtags -fuse-ld=gold -m64 -Wl,-O1 -Wl,--as-needed -Wl,--gc-sections -o mksnapshot -Wl,--start-group obj.host/v8/src/snapshot/mksnapshot.mksnapshot.o obj.host/v8/tools/gyp/libv8_base.a obj.host/v8/tools/gyp/libv8_nosnapshot.a obj.host/v8/tools/gyp/libv8_libplatform.a obj.host/third_party/icu/libicui18n.a obj.host/third_party/icu/libicuuc.a obj.host/v8/tools/gyp/libv8_libbase.a -Wl,--end-group  -ldl -lrt
chromeos-chrome-51.0.2679.0_rc-r1: /usr/x86_64-pc-linux-gnu/binutils-bin/2.25.51/ld.gold.real: internal error in make_view, at /var/tmp/portage/sys-devel/binutils-2.25.51-r56/work/binutils-2.25.51/binutils-2.25/gold/fileread.cc:474
chromeos-chrome-51.0.2679.0_rc-r1: collect2: error: ld returned 1 exit status

(See https://uberchromegw.corp.google.com/i/chromeos/builders/glados-release-group/builds/810/steps/BuildPackages%20%5Bcave%5D%20%5Bafdo_use%5D/logs/stdio )

The same builder succeeds on the same run for the Chell board. As far as I can tell from a quick glance there should be no difference between the two boards that would affect Chrome compilation in any way, but I may have missed something.

Comment 1 by bhthompson@chromium.org, Mar 23 2016

Cc: josephsih@chromium.org dgreid@chromium.org
Owner: ttsang@chromium.org
+sheriffs

Cave should be building essentially the same as Chell, so I am not sure what we could be doing wrong here. My initial inclination is to clobber this builder and see if it recovers as a first step.

It is possible we had a situation where half the overlay was in place when it first started building and it is stuck in an odd state.

Comment 2 by bhthompson@chromium.org, Mar 25 2016 

It is still broken, clobber did not help. 

We need to do some digging on this one, deeper comparison of what is configured differently in Cave from Chell, possibly with a local repro case.

Comment 3 by agnescheng@chromium.org, Apr 6 2016 

Friendly ping - Canary is still failed. Firmware and factory builders can work. Should/could we re-create the builder?

Comment 4 by bhthompson@chromium.org, Apr 6 2016

Cc: d...@chromium.org vadimsh@chromium.org
+dnj, vadimsh

It appears the glados-b build group (which now contains cave) is offline, I think the troopers need to do something to bring it up.

https://uberchromegw.corp.google.com/i/chromeos/builders/glados-b-release-group

Comment 5 by d...@chromium.org, Apr 6 2016

Labels: Infra-Troopers
Owner: ----
This seems like an odd bug to ping, since this build group has existed for less than one day.

That said, yes the builder needs to be brought up. Adding to trooper queue for this.

Comment 6 by d...@chromium.org, Apr 6 2016

Status: Fixed (was: Untriaged)
Actually trooper is already on this, marking Fixed.

Comment 7 by patricia@chromium.org, Apr 11 2016

Labels: VerifyIn-51

Comment 8 by patricia@chromium.org, May 23 2016

Status: Verified (was: Fixed)
Bulk verified
►

Sign in to add a comment