From: catalyst@guppy.ia64.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [ia64-auto] Catalyst fatal build error - stage2.spec
Date: Sat, 31 Aug 2019 06:53:21 +0000 [thread overview]
Message-ID: <20190831064730.182E1E0829@pigeon.gentoo.org> (raw)
*** Running command: catalyst -a -c /etc/catalyst/catalyst.conf -f stage2.spec
31 Aug 2019 06:50:30 UTC: NOTICE : Loading configuration file: /etc/catalyst/catalyst.conf
31 Aug 2019 06:50:30 UTC: NOTICE : conf_values[options] = {'seedcache', 'clear-autoresume', 'snapcache', 'autoresume', 'pkgcache', 'kerncache', 'bindist'}
31 Aug 2019 06:50:30 UTC: NOTICE : Processing spec file: stage2.spec
31 Aug 2019 06:50:30 UTC: NOTICE : Using target: stage2
31 Aug 2019 06:50:30 UTC: NOTICE : Source file specification matching setting is: strict
31 Aug 2019 06:50:30 UTC: NOTICE : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
31 Aug 2019 06:50:30 UTC: NOTICE : Source path set to /var/tmp/catalyst/tmp/default/stage1-ia64-20190831T031002Z/
31 Aug 2019 06:50:30 UTC: NOTICE : Removing AutoResume Points ...
31 Aug 2019 06:50:30 UTC: NOTICE : Emptying directory: /var/tmp/catalyst/tmp/default/.autoresume-stage2-ia64-20190831T031002Z
31 Aug 2019 06:50:30 UTC: NOTICE : --- Running action sequence: unpack
31 Aug 2019 06:50:30 UTC: NOTICE : Resume: "seed source" unpack resume point is disabled
31 Aug 2019 06:50:30 UTC: NOTICE : Resume: Target chroot is invalid, cleaning up...
31 Aug 2019 06:50:30 UTC: NOTICE : Removing AutoResume Points ...
31 Aug 2019 06:50:30 UTC: NOTICE : Emptying directory: /var/tmp/catalyst/tmp/default/.autoresume-stage2-ia64-20190831T031002Z
31 Aug 2019 06:50:30 UTC: NOTICE : Clearing the chroot path ...
31 Aug 2019 06:50:30 UTC: NOTICE : Emptying directory: /var/tmp/catalyst/tmp/default/stage2-ia64-20190831T031002Z
31 Aug 2019 06:50:30 UTC: NOTICE : Starting rsync from /var/tmp/catalyst/tmp/default/stage1-ia64-20190831T031002Z/
31 Aug 2019 06:50:30 UTC: NOTICE : to /var/tmp/catalyst/tmp/default/stage2-ia64-20190831T031002Z (this may take some time) ..
31 Aug 2019 06:53:20 UTC: NOTICE : --- Running action sequence: unpack_snapshot
31 Aug 2019 06:53:20 UTC: NOTICE : --- Running action sequence: setup_confdir
31 Aug 2019 06:53:21 UTC: NOTICE : --- Running action sequence: portage_overlay
31 Aug 2019 06:53:21 UTC: NOTICE : --- Running action sequence: base_dirs
31 Aug 2019 06:53:21 UTC: NOTICE : --- Running action sequence: bind
31 Aug 2019 06:53:21 UTC: NOTICE : --- Running action sequence: chroot_setup
31 Aug 2019 06:53:21 UTC: NOTICE : Setting up chroot...
31 Aug 2019 06:53:21 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
31 Aug 2019 06:53:21 UTC: WARNING : If your build fails look here first as the possible problem.
31 Aug 2019 06:53:21 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
31 Aug 2019 06:53:21 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
31 Aug 2019 06:53:21 UTC: WARNING : You have been warned.
31 Aug 2019 06:53:21 UTC: NOTICE : Writing the stage make.conf to: /var/tmp/catalyst/tmp/default/stage2-ia64-20190831T031002Z/etc/portage/make.conf
31 Aug 2019 06:53:21 UTC: NOTICE : STICKY-CONFIG is enabled
31 Aug 2019 06:53:21 UTC: NOTICE : --- Running action sequence: setup_environment
31 Aug 2019 06:53:21 UTC: NOTICE : --- Running action sequence: run_local
Copying stage2-chroot.sh to /tmp
copying stage2-chroot.sh to /var/tmp/catalyst/tmp/default/stage2-ia64-20190831T031002Z/tmp
copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/stage2-ia64-20190831T031002Z/tmp
Ensure the file has the executable bit set
Running stage2-chroot.sh in chroot:
chroot /var/tmp/catalyst/tmp/default/stage2-ia64-20190831T031002Z /tmp/stage2-chroot.sh
chroot: failed to run command './tmp/stage2-chroot.sh': No such file or directory
31 Aug 2019 06:53:21 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage2/stage2-controller.sh', 'run']) exited 1
31 Aug 2019 06:53:21 UTC: ERROR : CatalystError: Stage build aborting due to error.
31 Aug 2019 06:53:21 UTC: ERROR : Exception running action sequence run_local
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/catalyst/base/stagebase.py", line 1360, in run_local
env=self.env)
File "/usr/lib/python3.6/site-packages/catalyst/support.py", line 54, in cmd
print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage2/stage2-controller.sh', 'run']) exited 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/catalyst/base/stagebase.py", line 1465, in run
getattr(self, x)()
File "/usr/lib/python3.6/site-packages/catalyst/base/stagebase.py", line 1369, in run_local
print_traceback=False)
catalyst.support.CatalystError: Stage build aborting due to error.
31 Aug 2019 06:53:21 UTC: NOTICE : Cleaning up... Running unbind()
Full build log at /tmp/catalyst-auto.20190831T031002Z.MwwW3n/log/stage2.log
next reply other threads:[~2019-08-31 6:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-31 6:53 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-05 6:55 [gentoo-releng-autobuilds] [ia64-auto] Catalyst fatal build error - stage2.spec catalyst
2019-09-04 6:49 catalyst
2019-09-03 6:53 catalyst
2019-09-02 7:52 catalyst
2019-09-01 6:48 catalyst
2019-08-30 6:52 catalyst
2019-08-29 7:07 catalyst
2019-08-28 7:10 catalyst
2019-08-27 7:01 catalyst
2019-08-26 6:59 catalyst
2019-08-25 7:02 catalyst
2019-08-24 7:04 catalyst
2019-08-23 7:00 catalyst
2019-08-22 7:07 catalyst
2019-05-01 12:48 catalyst
2013-03-19 11:49 catalyst
2013-02-26 13:13 catalyst
2013-02-12 10:56 catalyst
2011-11-22 11:52 catalyst
2011-10-25 14:51 catalyst
2011-10-18 10:42 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=20190831064730.182E1E0829@pigeon.gentoo.org \
--to=catalyst@guppy.ia64.dev.gentoo.org \
--cc=gentoo-releng-autobuilds@lists.gentoo.org \
--cc=releng@gentoo.org \
/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