| 1 |
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-auto.conf -f stage1-x32.spec |
| 2 |
21 Feb 2018 00:01:09 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf |
| 3 |
21 Feb 2018 00:01:09 UTC: NOTICE : conf_values[options] = {'seedcache', 'clear-autoresume', 'preserve_libs', 'snapcache', 'pkgcache', 'bindist', 'autoresume'} |
| 4 |
21 Feb 2018 00:01:09 UTC: NOTICE : Processing spec file: stage1-x32.spec |
| 5 |
21 Feb 2018 00:01:09 UTC: NOTICE : Using target: stage1 |
| 6 |
21 Feb 2018 00:01:09 UTC: NOTICE : Source file specification matching setting is: loose |
| 7 |
21 Feb 2018 00:01:09 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz'] |
| 8 |
21 Feb 2018 00:01:11 UTC: NOTICE : Source path set to /release/buildroot/amd64-dev/builds/default/stage3-x32-latest.tar.xz |
| 9 |
21 Feb 2018 00:01:11 UTC: NOTICE : stage1 stage path is /release/buildroot/amd64-dev/tmp/default/stage1-x32-20180220T214502Z/tmp/stage1root |
| 10 |
21 Feb 2018 00:01:11 UTC: NOTICE : Removing AutoResume Points ... |
| 11 |
21 Feb 2018 00:01:11 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/default/.autoresume-stage1-x32-20180220T214502Z |
| 12 |
21 Feb 2018 00:01:11 UTC: NOTICE : --- Running action sequence: unpack |
| 13 |
21 Feb 2018 00:01:11 UTC: NOTICE : Referenced SEEDCACHE does not appear to be a directory, trying to untar... |
| 14 |
21 Feb 2018 00:01:11 UTC: NOTICE : Resume: "seed source" unpack resume point is disabled |
| 15 |
21 Feb 2018 00:01:11 UTC: NOTICE : Resume: Target chroot is invalid, cleaning up... |
| 16 |
21 Feb 2018 00:01:11 UTC: NOTICE : Removing AutoResume Points ... |
| 17 |
21 Feb 2018 00:01:11 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/default/.autoresume-stage1-x32-20180220T214502Z |
| 18 |
21 Feb 2018 00:01:11 UTC: NOTICE : Clearing the chroot path ... |
| 19 |
21 Feb 2018 00:01:11 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/default/stage1-x32-20180220T214502Z |
| 20 |
21 Feb 2018 00:01:11 UTC: NOTICE : Starting auto from /release/buildroot/amd64-dev/builds/default/stage3-x32-latest.tar.xz |
| 21 |
21 Feb 2018 00:01:11 UTC: NOTICE : to /release/buildroot/amd64-dev/tmp/default/stage1-x32-20180220T214502Z (this may take some time) .. |
| 22 |
21 Feb 2018 00:01:29 UTC: NOTICE : --- Running action sequence: unpack_snapshot |
| 23 |
21 Feb 2018 00:01:29 UTC: NOTICE : --- Running action sequence: setup_confdir |
| 24 |
21 Feb 2018 00:01:29 UTC: NOTICE : --- Running action sequence: portage_overlay |
| 25 |
21 Feb 2018 00:01:29 UTC: NOTICE : --- Running action sequence: base_dirs |
| 26 |
21 Feb 2018 00:01:29 UTC: NOTICE : --- Running action sequence: bind |
| 27 |
21 Feb 2018 00:01:29 UTC: NOTICE : --- Running action sequence: chroot_setup |
| 28 |
21 Feb 2018 00:01:29 UTC: NOTICE : Setting up chroot... |
| 29 |
21 Feb 2018 00:01:29 UTC: WARNING : Overriding certain env variables may cause catastrophic failure. |
| 30 |
21 Feb 2018 00:01:29 UTC: WARNING : If your build fails look here first as the possible problem. |
| 31 |
21 Feb 2018 00:01:29 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables. |
| 32 |
21 Feb 2018 00:01:29 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all. |
| 33 |
21 Feb 2018 00:01:29 UTC: WARNING : You have been warned. |
| 34 |
21 Feb 2018 00:01:29 UTC: NOTICE : Writing the stage make.conf to: /release/buildroot/amd64-dev/tmp/default/stage1-x32-20180220T214502Z/etc/portage/make.conf |
| 35 |
21 Feb 2018 00:01:29 UTC: NOTICE : STICKY-CONFIG is enabled |
| 36 |
21 Feb 2018 00:01:29 UTC: NOTICE : --- Running action sequence: setup_environment |
| 37 |
21 Feb 2018 00:01:29 UTC: NOTICE : --- Running action sequence: run_local |
| 38 |
copying make.conf to /release/buildroot/amd64-dev/tmp/default/stage1-x32-20180220T214502Z/tmp/stage1root/etc/portage |
| 39 |
Copying stage1-chroot.sh to /tmp |
| 40 |
copying stage1-chroot.sh to /release/buildroot/amd64-dev/tmp/default/stage1-x32-20180220T214502Z/tmp |
| 41 |
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/default/stage1-x32-20180220T214502Z/tmp |
| 42 |
Ensure the file has the executable bit set |
| 43 |
Running stage1-chroot.sh in chroot: |
| 44 |
chroot /release/buildroot/amd64-dev/tmp/default/stage1-x32-20180220T214502Z /tmp/stage1-chroot.sh |
| 45 |
>>> Regenerating /etc/ld.so.cache... |
| 46 |
Adding USE="${USE} build" to make.conf for portage build |
| 47 |
emerge --quiet --oneshot --update --newuse sys-apps/portage |
| 48 |
|
| 49 |
Performing Global Updates |
| 50 |
(Could take a couple of minutes if you have a lot of binary packages.) |
| 51 |
|
| 52 |
|
| 53 |
>>> Verifying ebuild manifests |
| 54 |
>>> Emerging (1 of 1) sys-apps/portage-2.3.24-r1::gentoo |
| 55 |
>>> Failed to emerge sys-apps/portage-2.3.24-r1 |
| 56 |
* Messages for package sys-apps/portage-2.3.24-r1: |
| 57 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
| 58 |
* is known to be triggered by things such as failed variable assignments |
| 59 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
| 60 |
* exiting, bash should have displayed an error message above. If bash did |
| 61 |
* not produce an error message above, it's possible that the ebuild has |
| 62 |
* called `exit` when it should have called `die` instead. This behavior |
| 63 |
* may also be triggered by a corrupt bash binary or a hardware problem |
| 64 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
| 65 |
* it appears to occur randomly, then it is likely to be triggered by a |
| 66 |
* hardware problem. If you suspect a hardware problem then you should try |
| 67 |
* some basic hardware diagnostics such as memtest. Please do not report |
| 68 |
* this as a bug unless it is consistently reproducible and you are sure |
| 69 |
* that your bash binary and hardware are functioning properly. |
| 70 |
|
| 71 |
|
| 72 |
21 Feb 2018 00:01:38 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 |
| 73 |
21 Feb 2018 00:01:38 UTC: ERROR : CatalystError: Stage build aborting due to error. |
| 74 |
21 Feb 2018 00:01:38 UTC: ERROR : Exception running action sequence run_local |
| 75 |
Traceback (most recent call last): |
| 76 |
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1354, in run_local |
| 77 |
env=self.env) |
| 78 |
File "/usr/lib64/python3.4/site-packages/catalyst/support.py", line 54, in cmd |
| 79 |
print_traceback=False) |
| 80 |
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 |
| 81 |
|
| 82 |
During handling of the above exception, another exception occurred: |
| 83 |
|
| 84 |
Traceback (most recent call last): |
| 85 |
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1454, in run |
| 86 |
getattr(self, x)() |
| 87 |
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1363, in run_local |
| 88 |
print_traceback=False) |
| 89 |
catalyst.support.CatalystError: Stage build aborting due to error. |
| 90 |
21 Feb 2018 00:01:38 UTC: NOTICE : Cleaning up... Running unbind() |
| 91 |
Command exited with non-zero status 2 |
| 92 |
28.36user 5.93system 0:29.11elapsed 117%CPU (0avgtext+0avgdata 1401952maxresident)k |
| 93 |
330824inputs+2178416outputs (0major+220588minor)pagefaults 0swaps |
| 94 |
|
| 95 |
|
| 96 |
|
| 97 |
Full build log at /release/tmp/run/catalyst-auto.20180220T214502Z.dczClf/log/stage1-x32.log |
Archives