From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-releng-autobuilds+bounces-8586-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by finch.gentoo.org (Postfix) with ESMTPS id D1DA0138334
for <garchives@archives.gentoo.org>; Wed, 27 Jun 2018 17:57:28 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 76D62E08EC;
Wed, 27 Jun 2018 17:57:27 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 3CF35E08EC
for <gentoo-releng-autobuilds@lists.gentoo.org>; Wed, 27 Jun 2018 17:57:25 +0000 (UTC)
Received: from guppy (unknown [IPv6:2001:470:ea4a:1:217:a4ff:fe51:cf57])
by smtp.gentoo.org (Postfix) with SMTP id 9C961335C7E;
Wed, 27 Jun 2018 17:57:24 +0000 (UTC)
Received: by guppy (sSMTP sendmail emulation); Wed, 27 Jun 2018 17:57:24 +0000
Date: Wed, 27 Jun 2018 17:57:24 +0000
From: catalyst@guppy.ia64.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [ia64-auto] Catalyst non-fatal build error - installcd-stage2-minimal.spec
Precedence: bulk
List-Post: <mailto:gentoo-releng-autobuilds@lists.gentoo.org>
List-Help: <mailto:gentoo-releng-autobuilds+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-releng-autobuilds+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-releng-autobuilds+subscribe@lists.gentoo.org>
List-Id: Gentoo Release Engineering Autobuilds <gentoo-releng-autobuilds.gentoo.org>
X-BeenThere: gentoo-releng-autobuilds@gentoo.org
X-BeenThere: gentoo-releng-autobuilds@lists.gentoo.org
Reply-To: gentoo-releng-autobuilds@lists.gentoo.org
Message-Id: <20180627175727.76D62E08EC@pigeon.gentoo.org>
X-Archives-Salt: 4ccd9487-00f9-4099-bb04-ffc99dc807a3
X-Archives-Hash: 3530a2588bb00ca27e4bf99cb993c9b9
*** Running command: time catalyst -a -c /etc/catalyst/catalyst.conf -f installcd-stage2-minimal.spec
Catalyst, version 2.0.18
Copyright 2003-2008 Gentoo Foundation
Copyright 2008-2012 various authors
Distributed under the GNU General Public License version 2.1
Using command line specified Catalyst configuration file, /etc/catalyst/catalyst.conf
Setting sharedir to config file value "/usr/lib/catalyst"
Setting snapshot_cache to config file value "/home/catalyst/snapshot_cache"
Setting hash_function to config file value "crc32"
Setting storedir to config file value "/home/catalyst"
Setting portdir to config file value "/usr/portage"
Setting distdir to config file value "/usr/portage/distfiles"
Setting options to config file value "autoresume bindist pkgcache seedcache snapcache"
Autoresuming support enabled.
Binary redistribution enabled
Package cache support enabled.
Seed cache support enabled.
Snapshot cache support enabled.
Envscript support enabled.
Using target: livecd-stage2
Building natively for ia64
Caching snapshot to /home/catalyst/snapshot_cache/20180627T031002Z/
The autoresume path is /home/catalyst/tmp/default/.autoresume-livecd-stage2-ia64-20180627T031002Z/
Location of the package cache is /home/catalyst/packages/default/livecd-stage2-ia64-20180627T031002Z/
Checking for processes running in chroot and killing them.
Removing AutoResume Points: ...
Emptying directory /home/catalyst/tmp/default/.autoresume-livecd-stage2-ia64-20180627T031002Z/
--- Running action sequence: unpack
Starting rsync from /home/catalyst/tmp/default/livecd-stage1-ia64-20180627T031002Z/
to /home/catalyst/tmp/default/livecd-stage2-ia64-20180627T031002Z/ (This may take some time) ...
--- Running action sequence: unpack_snapshot
Valid snapshot cache, skipping unpack of portage tree...
--- Running action sequence: config_profile_link
Configuring profile link...
--- Running action sequence: setup_confdir
Configuring /etc/portage...
--- Running action sequence: portage_overlay
--- Running action sequence: bind
--- Running action sequence: chroot_setup
Setting up chroot...
Warning!!!!
Overriding certain env variables may cause catastrophic failure.
If your build fails look here first as the possible problem.
Catalyst assumes you know what you are doing when setting
these variables.
Catalyst Maintainers use VERY minimal envscripts if used at all
You have been warned
--- Running action sequence: setup_environment
--- Running action sequence: run_local
--- Running action sequence: build_kernel
Copying pre-kmerge.sh to /tmp
copying pre-kmerge.sh to /home/catalyst/tmp/default/livecd-stage2-ia64-20180627T031002Z//tmp
copying chroot-functions.sh to /home/catalyst/tmp/default/livecd-stage2-ia64-20180627T031002Z//tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot /home/catalyst/tmp/default/livecd-stage2-ia64-20180627T031002Z/
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot genkernel
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-kernel/genkernel-3.5.3.3
>>> Emerging (1 of 3) app-arch/cpio-2.12-r1::gentoo
>>> Installing (1 of 3) app-arch/cpio-2.12-r1::gentoo
>>> Emerging (2 of 3) sys-kernel/linux-firmware-20180103-r1::gentoo
>>> Installing (2 of 3) sys-kernel/linux-firmware-20180103-r1::gentoo
>>> Emerging (3 of 3) sys-kernel/genkernel-3.5.3.3::gentoo
>>> Installing (3 of 3) sys-kernel/genkernel-3.5.3.3::gentoo
* Messages for package sys-kernel/linux-firmware-20180103-r1:
* Your configuration for sys-kernel/linux-firmware-20180103-r1 has been saved in
* /etc/portage/savedconfig/sys-kernel/linux-firmware-20180103-r1 for your editing pleasure.
* You can edit these files by hand and remerge this package with
* USE=savedconfig to customise the configuration.
* You can rename this file/directory to one of the following for
* its configuration to apply to multiple versions:
* ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/
* [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}]
* If you are only interested in particular firmware files, edit the saved
* configfile and remove those that you do not want.
* Messages for package sys-kernel/genkernel-3.5.3.3:
* Documentation is available in the genkernel manual page
* as well as the following URL:
* https://wiki.gentoo.org/wiki/Genkernel
* This package is known to not work with reiser4. If you are running
* reiser4 and have a problem, do not file a bug. We know it does not
* work and we don't plan on fixing it since reiser4 is the one that is
* broken in this regard. Try using a sane filesystem like ext4.
* The LUKS support has changed from versions prior to 3.4.4. Now,
* you use crypt_root=/dev/blah instead of real_root=luks:/dev/blah.
removing /home/catalyst/tmp/default/livecd-stage2-ia64-20180627T031002Z//tmp/pre-kmerge.sh from the chroot
removing /home/catalyst/tmp/default/livecd-stage2-ia64-20180627T031002Z//tmp/chroot-functions.sh from the chroot
Copying kmerge.sh to /tmp
copying kmerge.sh to /home/catalyst/tmp/default/livecd-stage2-ia64-20180627T031002Z//tmp
copying chroot-functions.sh to /home/catalyst/tmp/default/livecd-stage2-ia64-20180627T031002Z//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /home/catalyst/tmp/default/livecd-stage2-ia64-20180627T031002Z/
>>> Regenerating /etc/ld.so.cache...
Genkernel version 3.5.3.3 found ... continuing
emerge --quiet --usepkg --buildpkg --newuse gentoo-sources
>>> Verifying ebuild manifests
>>> Emerging (1 of 2) sys-devel/bc-1.06.95-r2::gentoo
>>> Installing (1 of 2) sys-devel/bc-1.06.95-r2::gentoo
>>> Emerging (2 of 2) sys-kernel/gentoo-sources-4.9.95::gentoo
>>> Installing (2 of 2) sys-kernel/gentoo-sources-4.9.95::gentoo
>>> Recording sys-kernel/gentoo-sources in "world" favorites file...
* Messages for package sys-kernel/gentoo-sources-4.9.95:
* If you are upgrading from a previous kernel, you may be interested
* in the following document:
* - General upgrade guide: https://wiki.gentoo.org/wiki/Kernel/Upgrade
Error: --dmraid requires sys-fs/dmraid
to be installed on the host system.
!!! catalyst: Runscript kernel build failed
Traceback (most recent call last):
File "modules/generic_stage_target.py", line 1428, in build_kernel
self._build_kernel(kname=kname)
File "modules/generic_stage_target.py", line 1472, in _build_kernel
"Runscript kernel build failed",env=self.env)
File "/usr/lib/catalyst/modules/catalyst_support.py", line 541, in cmd
raise CatalystError,myexc
CatalystError
None
!!! catalyst: build aborting due to kernel build error.
Traceback (most recent call last):
File "/usr/lib/catalyst/catalyst", line 218, in build_target
mytarget.run()
File "modules/generic_stage_target.py", line 1304, in run
apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1433, in build_kernel
"build aborting due to kernel build error."
CatalystError
!!! catalyst: Error encountered during run of target livecd-stage2
Catalyst aborting....
lockfile does not exist '/home/catalyst/tmp/default/livecd-stage2-ia64-20180627T031002Z/.catalyst_lock'
Command exited with non-zero status 1
711.29user 113.62system 17:28.57elapsed 78%CPU (0avgtext+0avgdata 447472maxresident)k
0inputs+0outputs (132major+8675616minor)pagefaults 0swaps
Full build log at /tmp/catalyst-auto.20180627T031002Z.BXlkOE/log/installcd-stage2-minimal.log