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

Issue 629760 link

Starred by 2 users

Issue metadata

Status: Archived
Owner:
Closed: Sep 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

chromeos build failures due to Leak Detector

Project Member Reported by achuith@chromium.org, Jul 20 2016

Issue description

https://uberchromegw.corp.google.com/i/chromiumos.chromium/builders/x86-generic-tot-chromium-pfq-informational/builds/9133

Error log:
chromeos-chrome-54.0.2803.0_alpha-r1: FAILED: obj/chrome/renderer/leak_detector/leak_detector/leak_detector_remote_client.o 
chromeos-chrome-54.0.2803.0_alpha-r1: i686-pc-linux-gnu-g++ -B/usr/x86_64-pc-linux-gnu/i686-pc-linux-gnu/binutils-bin/2.25.51-gold -MMD -MF obj/chrome/renderer/leak_detector/leak_detector/leak_detector_remote_client.o.d -DV8_DEPRECATION_WARNINGS -DENABLE_MDNS=1 -DENABLE_NOTIFICATIONS -DENABLE_PEPPER_CDMS -DENABLE_PLUGINS=1 -DENABLE_PDF=1 -DENABLE_PRINTING=1 -DENABLE_BASIC_PRINTING=1 -DENABLE_PRINT_PREVIEW=1 -DENABLE_SPELLCHECK=1 -DUSE_UDEV -DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_ASH=1 -DUSE_AURA=1 -DUSE_DEFAULT_RENDER_THEME=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DENABLE_WEBRTC=1 -DENABLE_EXTENSIONS=1 -DENABLE_TASK_MANAGER=1 -DENABLE_THEMES=1 -DENABLE_CAPTIVE_PORTAL_DETECTION=1 -DENABLE_SESSION_SERVICE=1 -DENABLE_APP_LIST=1 -DENABLE_SUPERVISED_USERS=1 -DENABLE_SERVICE_DISCOVERY=1 -DIMAGE_LOADER_EXTENSION=1 -DENABLE_WAYLAND_SERVER=1 -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 -DFIELDTRIAL_TESTING_ENABLED -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DOS_CHROMEOS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DGOOGLE_PROTOBUF_NO_RTTI -DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD -I../../../../../../../home/chrome-bot/chrome_root/src -Igen -I../../../../../../../home/chrome-bot/chrome_root/src/third_party/protobuf/src -Igen/protoc_out -I../../../../../../../home/chrome-bot/chrome_root/src/third_party/protobuf/src -fno-strict-aliasing -funwind-tables -fPIC -pipe -pthread -m32 -msse2 -mfpmath=sse -mmmx -Wall -Werror -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident -fdata-sections -ffunction-sections -g2 -gsplit-dwarf --sysroot=../../../../../../../build/x86-generic -fvisibility=hidden -fno-threadsafe-statics -fvisibility-inlines-hidden -std=gnu++11 -Wno-narrowing -Wno-literal-suffix -fno-rtti -fno-exceptions -march=i686 -pipe -march=i686 -pipe -pipe -march=i686 -mfpmath=sse -mmmx -msse -msse2 -msse3 -D__google_stl_debug_vector=1  -c ../../../../../../../home/chrome-bot/chrome_root/src/chrome/renderer/leak_detector/leak_detector_remote_client.cc -o obj/chrome/renderer/leak_detector/leak_detector/leak_detector_remote_client.o
chromeos-chrome-54.0.2803.0_alpha-r1: In file included from ../../../../../../../home/chrome-bot/chrome_root/src/chrome/renderer/leak_detector/leak_detector_remote_client.cc:13:0:
chromeos-chrome-54.0.2803.0_alpha-r1: ../../../../../../../home/chrome-bot/chrome_root/src/services/shell/public/cpp/interface_provider.h:8:71: fatal error: services/shell/public/interfaces/interface_provider.mojom.h: No such file or directory
chromeos-chrome-54.0.2803.0_alpha-r1:  #include "services/shell/public/interfaces/interface_provider.mojom.h"


CL responsible:
https://codereview.chromium.org/2064463002
 
Cc: rbhagavatula@chromium.org jwer...@chromium.org wuchengli@chromium.org sque@chromium.org
 Issue 629757  has been merged into this issue.

Comment 2 by sque@chromium.org, Jul 20 2016

How could I have caught this error? I couldn't reproduce it when building using simple Chrome workflow for board=peppy. I don't think using x86-generic instead of peppy will make a difference.
It's possible that this only breaks with chromeos build_packages unfortunately. I don't know enough about your CL to know what's going on.
Cc: bashi@chromium.org
I could not reproduce it yesterday.  http://crbug.com/617492  hit the same problem. You can ask bashi@

Comment 5 by bashi@chromium.org, Jul 21 2016

Didn't take a look but it's likely to forget to add some deps to services/shell in your .gn or .gyp

Comment 6 by sque@chromium.org, Sep 26 2016

Status: Fixed (was: Assigned)
Fixed: https://codereview.chromium.org/2169763002/

Comment 7 by dchan@chromium.org, Oct 7 2016

Labels: VerifyIn-55

Comment 8 by dchan@google.com, Nov 19 2016

Labels: VerifyIn-56

Comment 9 by dchan@google.com, Jan 21 2017

Labels: VerifyIn-57

Comment 10 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58

Comment 11 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 12 by dchan@google.com, May 30 2017

Labels: VerifyIn-60
Labels: VerifyIn-61

Comment 14 by dchan@chromium.org, Oct 14 2017

Status: Archived (was: Fixed)

Sign in to add a comment