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

Issue 843297 link

Starred by 1 user
Status: Fixed
Owner:
gwendal@chromium.org
Closed: May 2018
Cc:
█ vpalatin@chromium.org
kerrnel@chromium.org
█ rspangler@chromium.org
vapier@chromium.org
adurbin@chromium.org
█ victoryang@google.com
allenwebb@chromium.org
█ wfrichar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

chromeos-ec-headers failed to build on eve-tot-chrome-pfq-informational due to missing pinweaver_types.h

Project Member Reported by derat@chromium.org, May 15 2018 
chromeos-ec-headers failed to build on eve-tot-chrome-pfq-informational at http://cros-goldeneye/chromeos/healthmonitoring/buildDetails?buildbucketId=8946440911650075872:

Started chromeos-base/chromeos-ec-headers-0.0.1-r14 (logged in /tmp/chromeos-ec-headers-0.0.1-r14-X9I14E)
=== Start output for job chromeos-ec-headers-0.0.1-r14 (0m10.9s) ===
chromeos-ec-headers-0.0.1-r14: >>> Emerging (1 of 1) chromeos-base/chromeos-ec-headers-0.0.1-r14::chromiumos for /build/eve/
chromeos-ec-headers-0.0.1-r14:  * Running stacked hooks for pre_pkg_setup
chromeos-ec-headers-0.0.1-r14:  *    sysroot_build_bin_dir ...
chromeos-ec-headers-0.0.1-r14:  [ ok ]
chromeos-ec-headers-0.0.1-r14:  * Running stacked hooks for post_pkg_setup
chromeos-ec-headers-0.0.1-r14:  *    python_eclass_hack ...
chromeos-ec-headers-0.0.1-r14:  [ ok ]
chromeos-ec-headers-0.0.1-r14:  * Running stacked hooks for pre_src_unpack
chromeos-ec-headers-0.0.1-r14:  *    python_multilib_setup ...
chromeos-ec-headers-0.0.1-r14:  [ ok ]
chromeos-ec-headers-0.0.1-r14: >>> Unpacking source...
chromeos-ec-headers-0.0.1-r14:  * /mnt/host/source/src/platform/ec is not at rev f11169fa8d1ec6f6982306727f0bf0c8a7bd410b
chromeos-ec-headers-0.0.1-r14: Cloning into '/build/eve/tmp/portage/chromeos-base/chromeos-ec-headers-0.0.1-r14/work/chromeos-ec-headers-0.0.1/platform/ec'...
chromeos-ec-headers-0.0.1-r14: done.
chromeos-ec-headers-0.0.1-r14: >>> Source unpacked in /build/eve/tmp/portage/chromeos-base/chromeos-ec-headers-0.0.1-r14/work
chromeos-ec-headers-0.0.1-r14:  * Running stacked hooks for post_src_unpack
chromeos-ec-headers-0.0.1-r14:  *    asan_init ...
chromeos-ec-headers-0.0.1-r14:  [ ok ]
chromeos-ec-headers-0.0.1-r14: >>> Preparing source in /build/eve/tmp/portage/chromeos-base/chromeos-ec-headers-0.0.1-r14/work/chromeos-ec-headers-0.0.1 ...
chromeos-ec-headers-0.0.1-r14: >>> Source prepared.
chromeos-ec-headers-0.0.1-r14: >>> Configuring source in /build/eve/tmp/portage/chromeos-base/chromeos-ec-headers-0.0.1-r14/work/chromeos-ec-headers-0.0.1 ...
chromeos-ec-headers-0.0.1-r14: >>> Source configured.
chromeos-ec-headers-0.0.1-r14: >>> Compiling source in /build/eve/tmp/portage/chromeos-base/chromeos-ec-headers-0.0.1-r14/work/chromeos-ec-headers-0.0.1 ...
chromeos-ec-headers-0.0.1-r14: >>> Source compiled.
chromeos-ec-headers-0.0.1-r14: >>> Test phase [not enabled]: chromeos-base/chromeos-ec-headers-0.0.1-r14
chromeos-ec-headers-0.0.1-r14:  * Running stacked hooks for pre_src_install
chromeos-ec-headers-0.0.1-r14:  *    tidy_setup ...
chromeos-ec-headers-0.0.1-r14:  [ ok ]
chromeos-ec-headers-0.0.1-r14: 
chromeos-ec-headers-0.0.1-r14: >>> Install chromeos-ec-headers-0.0.1-r14 into /build/eve/tmp/portage/chromeos-base/chromeos-ec-headers-0.0.1-r14/image/ category chromeos-base
chromeos-ec-headers-0.0.1-r14: Traceback (most recent call last):
chromeos-ec-headers-0.0.1-r14:   File "/usr/lib/portage/python2.7/doins.py", line 584, in <module>
chromeos-ec-headers-0.0.1-r14:     sys.exit(main(sys.argv[1:]))
chromeos-ec-headers-0.0.1-r14:   File "/usr/lib/portage/python2.7/doins.py", line 575, in main
chromeos-ec-headers-0.0.1-r14:     os.path.dirname(source)):
chromeos-ec-headers-0.0.1-r14:   File "/usr/lib/portage/python2.7/doins.py", line 423, in _doins
chromeos-ec-headers-0.0.1-r14:     return install_runner.install_file(source, os.path.dirname(dest))
chromeos-ec-headers-0.0.1-r14:   File "/usr/lib/portage/python2.7/doins.py", line 359, in install_file
chromeos-ec-headers-0.0.1-r14:     return self._ins_runner.run(source, dest_dir)
chromeos-ec-headers-0.0.1-r14:   File "/usr/lib/portage/python2.7/doins.py", line 167, in run
chromeos-ec-headers-0.0.1-r14:     if not self._is_install_allowed(source, dest):
chromeos-ec-headers-0.0.1-r14:   File "/usr/lib/portage/python2.7/doins.py", line 214, in _is_install_allowed
chromeos-ec-headers-0.0.1-r14:     source_stat = os.stat(source)
chromeos-ec-headers-0.0.1-r14: OSError: [Errno 2] No such file or directory: 'include/pinweaver_types.h'
chromeos-ec-headers-0.0.1-r14:  * ERROR: chromeos-base/chromeos-ec-headers-0.0.1-r14::chromiumos failed (install phase):
chromeos-ec-headers-0.0.1-r14:  *   doins failed
chromeos-ec-headers-0.0.1-r14:  * 
chromeos-ec-headers-0.0.1-r14:  * If you need support, post the output of `emerge --info '=chromeos-base/chromeos-ec-headers-0.0.1-r14::chromiumos'`,
chromeos-ec-headers-0.0.1-r14:  * the complete build log and the output of `emerge -pqv '=chromeos-base/chromeos-ec-headers-0.0.1-r14::chromiumos'`.
chromeos-ec-headers-0.0.1-r14:  * The complete build log is located at '/build/eve/tmp/portage/logs/chromeos-base:chromeos-ec-headers-0.0.1-r14:20180515-192532.log'.
chromeos-ec-headers-0.0.1-r14:  * For convenience, a symlink to the build log is located at '/build/eve/tmp/portage/chromeos-base/chromeos-ec-headers-0.0.1-r14/temp/build.log'.
chromeos-ec-headers-0.0.1-r14:  * The ebuild environment file is located at '/build/eve/tmp/portage/chromeos-base/chromeos-ec-headers-0.0.1-r14/temp/environment'.
chromeos-ec-headers-0.0.1-r14:  * Working directory: '/build/eve/tmp/portage/chromeos-base/chromeos-ec-headers-0.0.1-r14/work/chromeos-ec-headers-0.0.1'
chromeos-ec-headers-0.0.1-r14:  * S: '/build/eve/tmp/portage/chromeos-base/chromeos-ec-headers-0.0.1-r14/work/chromeos-ec-headers-0.0.1'
chromeos-ec-headers-0.0.1-r14: >>> Failed to emerge chromeos-base/chromeos-ec-headers-0.0.1-r14 for /build/eve/, Log file:
chromeos-ec-headers-0.0.1-r14: >>>  '/build/eve/tmp/portage/logs/chromeos-base:chromeos-ec-headers-0.0.1-r14:20180515-192532.log'
chromeos-ec-headers-0.0.1-r14: 
chromeos-ec-headers-0.0.1-r14:  * Messages for package chromeos-base/chromeos-ec-headers-0.0.1-r14 merged to /build/eve/:
chromeos-ec-headers-0.0.1-r14: 
chromeos-ec-headers-0.0.1-r14:  * /mnt/host/source/src/platform/ec is not at rev f11169fa8d1ec6f6982306727f0bf0c8a7bd410b
chromeos-ec-headers-0.0.1-r14:  * ERROR: chromeos-base/chromeos-ec-headers-0.0.1-r14::chromiumos failed (install phase):
chromeos-ec-headers-0.0.1-r14:  *   doins failed
chromeos-ec-headers-0.0.1-r14:  * 
chromeos-ec-headers-0.0.1-r14:  * If you need support, post the output of `emerge --info '=chromeos-base/chromeos-ec-headers-0.0.1-r14::chromiumos'`,
chromeos-ec-headers-0.0.1-r14:  * the complete build log and the output of `emerge -pqv '=chromeos-base/chromeos-ec-headers-0.0.1-r14::chromiumos'`.
chromeos-ec-headers-0.0.1-r14:  * The complete build log is located at '/build/eve/tmp/portage/logs/chromeos-base:chromeos-ec-headers-0.0.1-r14:20180515-192532.log'.
chromeos-ec-headers-0.0.1-r14:  * For convenience, a symlink to the build log is located at '/build/eve/tmp/portage/chromeos-base/chromeos-ec-headers-0.0.1-r14/temp/build.log'.
chromeos-ec-headers-0.0.1-r14:  * The ebuild environment file is located at '/build/eve/tmp/portage/chromeos-base/chromeos-ec-headers-0.0.1-r14/temp/environment'.
chromeos-ec-headers-0.0.1-r14:  * Working directory: '/build/eve/tmp/portage/chromeos-base/chromeos-ec-headers-0.0.1-r14/work/chromeos-ec-headers-0.0.1'
chromeos-ec-headers-0.0.1-r14:  * S: '/build/eve/tmp/portage/chromeos-base/chromeos-ec-headers-0.0.1-r14/work/chromeos-ec-headers-0.0.1'
=== Complete: job chromeos-ec-headers-0.0.1-r14 (0m10.9s) ===
Failed chromeos-base/chromeos-ec-headers-0.0.1-r14 (in 0m10.9s). Your build has failed.

Comment 1 by vpalatin@google.com, May 15 2018 

my own anecdote: I got the same issue on my local build and 'solved' it by doing 'cros_workon-<board> start chromeos-ec-headers && emerge-<board> chromeos-ec-board
Not sure why this was needed

Comment 3 by derat@chromium.org, May 15 2018

Owner: gwendal@chromium.org
Status: Started (was: Assigned)
Thanks!

Comment 4 by allenwebb@chromium.org, May 15 2018

Cc: vapier@chromium.org
+vapier@ Is there anything we can do, to make errors like this get caught in the PreCQ / CQ?

Comment 5 by adurbin@chromium.org, May 15 2018

Cc: adurbin@chromium.org
We had a workaround to put 'platform/ec' in the prefix path of the install part of the ebuild.
Project Member

Comment 6 by bugdroid1@chromium.org, May 16 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/2b10d8e6846a99da07227fa4b0c513bfa89a23b9

commit 2b10d8e6846a99da07227fa4b0c513bfa89a23b9
Author: Gwendal Grignou <gwendal@chromium.org>
Date: Wed May 16 19:41:47 2018

FIXUP: trunks: added pinweaver_client binary

Fix error when compiling non-9999 version:

>>> Install chromeos-ec-headers-0.0.1-r14 into /build/eve-arcnext/tmp/portage/\
chromeos-base/chromeos-ec-headers-0.0.1-r14/image/ category chromeos-base
Traceback (most recent call last):
  File "/usr/lib/portage/python2.7/doins.py", line 584, in <module>
    sys.exit(main(sys.argv[1:]))
  File "/usr/lib/portage/python2.7/doins.py", line 575, in main
    os.path.dirname(source)):
  File "/usr/lib/portage/python2.7/doins.py", line 423, in _doins
    return install_runner.install_file(source, os.path.dirname(dest))
  File "/usr/lib/portage/python2.7/doins.py", line 359, in install_file
    return self._ins_runner.run(source, dest_dir)
  File "/usr/lib/portage/python2.7/doins.py", line 167, in run
    if not self._is_install_allowed(source, dest):
  File "/usr/lib/portage/python2.7/doins.py", line 214, in _is_install_allowed
    source_stat = os.stat(source)
OSError: [Errno 2] No such file or directory: 'include/pinweaver_types.h'
 * ERROR: chromeos-base/chromeos-ec-headers-0.0.1-r14::chromiumos failed (install phase):
 *   doins failed

BUG=chromium:808688, chromium:843297 
TEST=Check that without the fix we have an error.
Modify the named ebuild manually (chromeos-ec-headers-0.0.1-r14.ebuild)
to see the error is fixed.

Change-Id: Ib29a9ae33d8e3b60920d14a828f8950923e4d27f
Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1060171
Commit-Ready: Allen Webb <allenwebb@google.com>
Tested-by: Gwendal Grignou <gwendal@google.com>
Reviewed-by: Allen Webb <allenwebb@google.com>
Reviewed-by: Gwendal Grignou <gwendal@google.com>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/2b10d8e6846a99da07227fa4b0c513bfa89a23b9/chromeos-base/chromeos-ec-headers/chromeos-ec-headers-9999.ebuild

Comment 7 by derat@chromium.org, May 16 2018

Status: Fixed (was: Started)
►

Sign in to add a comment