From: catalyst@lantean.jmbsvicetto.name
To: jmbsvicetto@gmail.com,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [x86-auto] Catalyst non-fatal build error - hardened/admincd-stage2.spec
Date: Wed, 2 Apr 2014 14:40:47 +0000 (UTC) [thread overview]
Message-ID: <20140402144047.7D3C6FAE6D@lantean.jmbsvicetto.name> (raw)
Catalyst, version 2.0.15
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/release/x86-auto.conf
Setting sharedir to config file value "/usr/lib64/catalyst/"
Setting snapshot_cache to config file value "/home/release/tmp/snapshots"
Setting hash_function to config file value "crc32"
Setting storedir to config file value "/home/release/buildroot/x86-dev"
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 preserve_libs seedcache snapcache"
Autoresuming support enabled.
Binary redistribution enabled
Package cache support enabled.
Preserving libs during unmerge.
Seed cache support enabled.
Snapshot cache support enabled.
Envscript support enabled.
Using target: livecd-stage2
Building on amd64 for alternate personality type x86
Caching snapshot to /home/release/tmp/snapshots/20140402/
The autoresume path is /home/release/buildroot/x86-dev/tmp/hardened/.autoresume-livecd-stage2-x86-20140402/
Location of the package cache is /home/release/buildroot/x86-dev/packages/hardened/livecd-stage2-x86-20140402/
Checking for processes running in chroot and killing them.
Removing AutoResume Points: ...
Emptying directory /home/release/buildroot/x86-dev/tmp/hardened/.autoresume-livecd-stage2-x86-20140402/
>>> Waiting 10 seconds before starting...
>>> (Control-C to abort)...
Purging Caches ... in: 10 9 8 7 6 5 4 3 2 1
clearing autoresume ...
Removing AutoResume Points: ...
Emptying directory /home/release/buildroot/x86-dev/tmp/hardened/.autoresume-livecd-stage2-x86-20140402/
clearing chroot ...
Emptying directory /home/release/buildroot/x86-dev/tmp/hardened/livecd-stage2-x86-20140402/
clearing package cache ...
purging the pkgcache ...
clearing kerncache ...
--- Running action sequence: unpack
Starting rsync from /home/release/buildroot/x86-dev/tmp/hardened/livecd-stage1-x86-20140402/
to /home/release/buildroot/x86-dev/tmp/hardened/livecd-stage2-x86-20140402/ (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/release/buildroot/x86-dev/tmp/hardened/livecd-stage2-x86-20140402/./tmp
copying chroot-functions.sh to /home/release/buildroot/x86-dev/tmp/hardened/livecd-stage2-x86-20140402/./tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot /home/release/buildroot/x86-dev/tmp/hardened/livecd-stage2-x86-20140402/
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot genkernel
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-kernel/genkernel-3.4.45.1
>>> Installing (1 of 1) sys-kernel/genkernel-3.4.45.1
* Messages for package sys-kernel/genkernel-3.4.45.1:
* Copying files to /var/cache/genkernel/src...
* Documentation is available in the genkernel manual page
* as well as the following URL:
* http://www.gentoo.org/doc/en/genkernel.xml
* 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 ext3 or
* even reiser3.
* 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.
* Local use flag 'crypt' has been renamed to 'cryptsetup' (bug #414523).
* Please set flag 'cryptsetup' for this very package if you would like
* to have genkernel create an initramfs with LUKS support.
* Sorry for the inconvenience.
removing /home/release/buildroot/x86-dev/tmp/hardened/livecd-stage2-x86-20140402/./tmp/pre-kmerge.sh from the chroot
removing /home/release/buildroot/x86-dev/tmp/hardened/livecd-stage2-x86-20140402/./tmp/chroot-functions.sh from the chroot
Copying kmerge.sh to ./tmp
copying kmerge.sh to /home/release/buildroot/x86-dev/tmp/hardened/livecd-stage2-x86-20140402/./tmp
copying chroot-functions.sh to /home/release/buildroot/x86-dev/tmp/hardened/livecd-stage2-x86-20140402/./tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /home/release/buildroot/x86-dev/tmp/hardened/livecd-stage2-x86-20140402/
>>> Regenerating /etc/ld.so.cache...
Genkernel version 3.4.45.1 found ... continuing
emerge --quiet --usepkg --buildpkg --newuse hardened-sources
>>> Verifying ebuild manifests
>>> Emerging (1 of 2) sys-devel/bc-1.06.95
>>> Installing (1 of 2) sys-devel/bc-1.06.95
>>> Emerging (2 of 2) sys-kernel/hardened-sources-3.13.2-r3
Traceback (most recent call last):
File "/usr/bin/emerge", line 50, in <module>
retval = emerge_main()
File "/usr/lib/portage/pym/_emerge/main.py", line 1031, in emerge_main
return run_action(emerge_config)
File "/usr/lib/portage/pym/_emerge/actions.py", line 4062, in run_action
emerge_config.args, spinner)
File "/usr/lib/portage/pym/_emerge/actions.py", line 453, in action_build
retval = mergetask.merge()
File "/usr/lib/portage/pym/_emerge/Scheduler.py", line 1019, in merge
rval = self._merge()
File "/usr/lib/portage/pym/_emerge/Scheduler.py", line 1408, in _merge
self._main_loop()
File "/usr/lib/portage/pym/_emerge/Scheduler.py", line 1385, in _main_loop
self._event_loop.iteration()
File "/usr/lib/portage/pym/portage/util/_eventloop/EventLoop.py", line 268, in iteration
if not x.callback(f, event, *x.args):
File "/usr/lib/portage/pym/portage/util/_async/PipeLogger.py", line 131, in _output_handler
log_file.flush()
OSError: [Errno 28] No space left on device
umount: /home/release/buildroot/x86-dev/tmp/hardened/livecd-stage2-x86-20140402/dev/pts: target is busy
(In some cases useful info about processes that
use the device is found by lsof(8) or fuser(1).)
!!! catalyst: Runscript kernel build failed
!!! catalyst: First attempt to unmount: /home/release/buildroot/x86-dev/tmp/hardened/livecd-stage2-x86-20140402//dev/pts failed.
!!! catalyst: Killing any pids still running in the chroot
Checking for processes running in chroot and killing them.
Killing process(es)
pid: process name
22225: /home/release/buildroot/x86-dev/tmp/hardened/livecd-stage2-x86-20140402/usr/bin/sandbox
22227: /home/release/buildroot/x86-dev/tmp/hardened/livecd-stage2-x86-20140402/bin/bash
22244: /home/release/buildroot/x86-dev/tmp/hardened/livecd-stage2-x86-20140402/bin/bash
22261: /home/release/buildroot/x86-dev/tmp/hardened/livecd-stage2-x86-20140402/usr/bin/xz
22262: /home/release/buildroot/x86-dev/tmp/hardened/livecd-stage2-x86-20140402/bin/tar
Press Ctrl-C within 10 seconds to abort
/usr/lib64/catalyst//targets/support/kill-chroot-pids.sh: line 56: kill: (22225) - No such process
/usr/lib64/catalyst//targets/support/kill-chroot-pids.sh: line 56: kill: (22227) - No such process
/usr/lib64/catalyst//targets/support/kill-chroot-pids.sh: line 56: kill: (22244) - No such process
/usr/lib64/catalyst//targets/support/kill-chroot-pids.sh: line 56: kill: (22261) - No such process
/usr/lib64/catalyst//targets/support/kill-chroot-pids.sh: line 56: kill: (22262) - No such process
Traceback (most recent call last):
File "modules/generic_stage_target.py", line 1427, in build_kernel
self._build_ke
Full build log at /home/release/tmp/run/catalyst-auto.15882/log/hardened_admincd-stage2.log
next reply other threads:[~2014-04-02 14:40 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 14:40 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-09 14:45 [gentoo-releng-autobuilds] [x86-auto] Catalyst non-fatal build error - hardened/admincd-stage2.spec catalyst
2014-04-16 15:03 catalyst
2014-04-23 14:39 catalyst
2014-05-07 15:54 catalyst
2014-05-14 15:03 catalyst
2014-12-31 14:21 catalyst
2015-01-14 12:24 catalyst
2015-01-21 11:50 catalyst
2015-10-06 17:28 catalyst
2015-10-07 18:45 catalyst
2015-10-13 16:42 catalyst
2015-10-14 18:15 catalyst
2015-10-20 16:41 catalyst
2015-10-21 18:07 catalyst
2015-10-27 17:56 catalyst
2015-11-03 16:42 catalyst
2015-11-10 16:41 catalyst
2015-11-17 16:18 catalyst
2015-11-24 16:55 catalyst
2015-12-08 16:39 catalyst
2015-12-15 17:21 catalyst
2015-12-22 16:55 catalyst
2016-10-25 17:40 catalyst
2016-12-06 18:48 catalyst
2016-12-13 18:15 catalyst
2017-01-03 18:15 catalyst
2017-01-10 17:47 catalyst
2017-01-17 18:44 catalyst
2017-01-24 18:39 catalyst
2017-01-31 18:47 catalyst
2017-02-07 18:38 catalyst
2017-02-14 18:41 catalyst
2017-03-07 19:20 catalyst
2019-04-10 8:28 catalyst
2019-04-10 11:45 catalyst
2019-04-13 7:16 catalyst
2019-04-20 7:18 catalyst
2019-04-24 7:26 catalyst
2019-04-24 10:06 catalyst
2019-12-07 9:21 catalyst
2020-05-14 19:50 catalyst
2020-05-16 0:57 catalyst
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140402144047.7D3C6FAE6D@lantean.jmbsvicetto.name \
--to=catalyst@lantean.jmbsvicetto.name \
--cc=gentoo-releng-autobuilds@lists.gentoo.org \
--cc=jmbsvicetto@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox