New issue
Advanced search Search tips

Issue 677297 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

authpolicy fails to build

Project Member Reported by tnagel@chromium.org, Dec 28 2016

Issue description

After repo sync today, authpolicy failed to build two times but succeeded at the third try.  (dosbin: /build/auron_paine/var/cache/portage/chromeos-base/authpolicy/out/Default/authpolicy_parser does not exist)  I think we should fix that to prevent random breakage for random people / the commit queue.

Retrying emerge of chromeos-base/authpolicy-9999.
Started chromeos-base/authpolicy-9999 (logged in /tmp/authpolicy-9999-LwH73x)
=== Start output for job authpolicy-9999 (0m4.1s) ===
authpolicy-9999: >>> Emerging (1 of 1) chromeos-base/authpolicy-9999::chromiumos for /build/auron_paine/
authpolicy-9999:  * Running stacked hooks for pre_pkg_setup
authpolicy-9999:  *    sysroot_build_bin_dir ...
authpolicy-9999:  [ ok ]
authpolicy-9999:  * Running stacked hooks for pre_src_unpack
authpolicy-9999:  *    python_multilib_setup ...
authpolicy-9999:  [ ok ]
authpolicy-9999: >>> Unpacking source...
authpolicy-9999:  * Using local source dir(s): /mnt/host/source/src/platform2
authpolicy-9999:  * path: /mnt/host/source/src/platform2
authpolicy-9999:  * destdir: /build/auron_paine/tmp/portage/chromeos-base/authpolicy-9999/work/authpolicy-9999
authpolicy-9999: >>> Source unpacked in /build/auron_paine/tmp/portage/chromeos-base/authpolicy-9999/work
authpolicy-9999:  * Running stacked hooks for post_src_unpack
authpolicy-9999:  *    asan_init ...
authpolicy-9999:  [ ok ]
authpolicy-9999: >>> Preparing source in /mnt/host/source/src/platform2/authpolicy ...
authpolicy-9999: >>> Source prepared.
authpolicy-9999: >>> Configuring source in /mnt/host/source/src/platform2/authpolicy ...
authpolicy-9999: /mnt/host/source/src/platform2/common-mk/platform2.py --libdir=/usr/lib64 --use_flags=abi_x86_64 amd64 cros-debug elibc_glibc kernel_linux userland_GNU --jobs=32 --action=configure --cache_dir=/build/auron_paine/var/cache/portage/chromeos-base/authpolicy /mnt/host/source/src/platform2/authpolicy/authpolicy.gyp
authpolicy-9999: >>> Source configured.
authpolicy-9999: >>> Compiling source in /mnt/host/source/src/platform2/authpolicy ...
authpolicy-9999: /mnt/host/source/src/platform2/common-mk/platform2.py --libdir=/usr/lib64 --use_flags=abi_x86_64 amd64 cros-debug elibc_glibc kernel_linux userland_GNU --jobs=32 --action=compile --cache_dir=/build/auron_paine/var/cache/portage/chromeos-base/authpolicy all
authpolicy-9999: ninja: Entering directory `/build/auron_paine/var/cache/portage/chromeos-base/authpolicy/out/Default'
authpolicy-9999: ninja: no work to do.
authpolicy-9999: >>> Source compiled.
authpolicy-9999: >>> Test phase [not enabled]: chromeos-base/authpolicy-9999
authpolicy-9999: 
authpolicy-9999: >>> Install authpolicy-9999 into /build/auron_paine/tmp/portage/chromeos-base/authpolicy-9999/image/ category chromeos-base
authpolicy-9999: !!! dosbin: /build/auron_paine/var/cache/portage/chromeos-base/authpolicy/out/Default/authpolicy_parser does not exist
authpolicy-9999:  * ERROR: chromeos-base/authpolicy-9999::chromiumos failed (install phase):
authpolicy-9999:  *   dosbin failed
authpolicy-9999:  * 
authpolicy-9999:  * If you need support, post the output of `emerge --info '=chromeos-base/authpolicy-9999::chromiumos'`,
authpolicy-9999:  * the complete build log and the output of `emerge -pqv '=chromeos-base/authpolicy-9999::chromiumos'`.
authpolicy-9999:  * The complete build log is located at '/build/auron_paine/tmp/portage/logs/chromeos-base:authpolicy-9999:20161228-141202.log'.
authpolicy-9999:  * For convenience, a symlink to the build log is located at '/build/auron_paine/tmp/portage/chromeos-base/authpolicy-9999/temp/build.log'.
authpolicy-9999:  * The ebuild environment file is located at '/build/auron_paine/tmp/portage/chromeos-base/authpolicy-9999/temp/environment'.
authpolicy-9999:  * Working directory: '/mnt/host/source/src/platform2/authpolicy'
authpolicy-9999:  * S: '/mnt/host/source/src/platform2/authpolicy'
authpolicy-9999:  * QA Notice: file does not exist:
authpolicy-9999:  * 
authpolicy-9999:  *     dosbin: /build/auron_paine/var/cache/portage/chromeos-base/authpolicy/out/Default/authpolicy_parser does not exist
authpolicy-9999: >>> Failed to emerge chromeos-base/authpolicy-9999 for /build/auron_paine/, Log file:
authpolicy-9999: >>>  '/build/auron_paine/tmp/portage/logs/chromeos-base:authpolicy-9999:20161228-141202.log'
authpolicy-9999: 
authpolicy-9999:  * Messages for package chromeos-base/authpolicy-9999 merged to /build/auron_paine/:
authpolicy-9999: 
authpolicy-9999:  * ERROR: chromeos-base/authpolicy-9999::chromiumos failed (install phase):
authpolicy-9999:  *   dosbin failed
authpolicy-9999:  * 
authpolicy-9999:  * If you need support, post the output of `emerge --info '=chromeos-base/authpolicy-9999::chromiumos'`,
authpolicy-9999:  * the complete build log and the output of `emerge -pqv '=chromeos-base/authpolicy-9999::chromiumos'`.
authpolicy-9999:  * The complete build log is located at '/build/auron_paine/tmp/portage/logs/chromeos-base:authpolicy-9999:20161228-141202.log'.
authpolicy-9999:  * For convenience, a symlink to the build log is located at '/build/auron_paine/tmp/portage/chromeos-base/authpolicy-9999/temp/build.log'.
authpolicy-9999:  * The ebuild environment file is located at '/build/auron_paine/tmp/portage/chromeos-base/authpolicy-9999/temp/environment'.
authpolicy-9999:  * Working directory: '/mnt/host/source/src/platform2/authpolicy'
authpolicy-9999:  * S: '/mnt/host/source/src/platform2/authpolicy'
=== Complete: job authpolicy-9999 (0m4.1s) ===
Failed chromeos-base/authpolicy-9999 (in 0m4.1s). Your build has failed.
 
This might happen if you are on a local branch of platform2, which would not be updated/rebased by a repo sync. You'd have to git rebase that branch first. Could this be the issue?

The commit queue would never have this problem because it would always be on the latest version. A random person might run into the same issue, but this is really the expected behavior.

Comment 2 by tnagel@chromium.org, Dec 28 2016

Thanks.  It's hard to tell now but I can't exclude it.  Feel free to close wontfix if you feel that's the most likely explanation.
Owner: ljusten@chromium.org
Guys, please assign an owner to chromad issues to keep them out of the general triage queue.
Status: WontFix (was: Untriaged)
The other explanation I can think of is that we don't build all targets, but I've never seen evidence of that in Chrome OS, so I'll close this one.
Labels: Enterprise-Triaged

Sign in to add a comment