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

Issue 760789 link

Starred by 1 user
Status: Verified
Owner:
█ renyi@chromium.org
Last visit > 30 days ago
Closed: Aug 2017
Cc:
█ renyi@chromium.org
ayatane@chromium.org
█ walker@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

whirlwind: missing include file "ap-daemons/vorlon/client/dbus-proxies.h"

Project Member Reported by mka@chromium.org, Aug 30 2017 
The whirlwind pre-cq builder fails in BuildPackages due to a missing include:

ap-daemons-0.0.3-r3204: /build/whirlwind/tmp/portage/chromeos-base/ap-daemons-0.0.3-r3204/work/ap-daemons-0.0.3/platform/ap-daemons/vorlon/rodizio/commands/command_manager.h:12:10: fatal error: 'ap-daemons/vorlon/client/dbus-proxies.h' file not found
ap-daemons-0.0.3-r3204: #include "ap-daemons/vorlon/client/dbus-proxies.h"

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

A missing dependency on 'vorlon-client-dbus-proxies' *might* be the issue

Comment 1 by mka@chromium.org, Aug 30 2017 

A similar case, with a different file:

platform/ap/api-server/tools/attestation_client.cc:9:10: fatal error: 'attestation/common/interface.pb.h' file not found

https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/no_vmtest_pre_cq/builds/109939

(not sure it is actually related, but better mention it since it's also missing include that just popped up now)
Project Member

Comment 2 by bugdroid1@chromium.org, Aug 31 2017 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/ap-daemons/+/8b876d832381074d005164b869eb02d6d89386ce

commit 8b876d832381074d005164b869eb02d6d89386ce
Author: Yi Ren <renyi@google.com>
Date: Thu Aug 31 00:24:37 2017

Comment 3 by zalcorn@chromium.org, Aug 31 2017

Components: Build

Comment 4 by mka@chromium.org, Aug 31 2017

Status: Verified (was: Assigned)
So far no more failures have been reported, apparently adding the dependency also fixed the case mentioned in #1.
►

Sign in to add a comment