Gentoo Archives: gentoo-releng-autobuilds

From: catalyst@×××××××××××××××××××××××.org
To: releng@g.o, gentoo-releng-autobuilds@l.g.o
Subject: [gentoo-releng-autobuilds] [ia64-auto] Catalyst fatal build error - stage1.spec
Date: Tue, 11 Oct 2011 06:40:00
Message-Id: 20111011063958.AB7D221C094@pigeon.gentoo.org
1 * error processing environment
2 /usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.4.5/temp/logging/other: No space left on device
3 *
4 /usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.4.5/temp/logging/other: No space left on device
5 * Call stack:
6 /usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.4.5/temp/logging/other: No space left on device
7 * misc-functions.sh, line 17: Called source '/usr/lib/portage/bin/ebuild.sh'
8 /usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.4.5/temp/logging/other: No space left on device
9 * ebuild.sh, line 1951: Called die
10 /usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.4.5/temp/logging/other: No space left on device
11 * The specific snippet of code:
12 /usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.4.5/temp/logging/other: No space left on device
13 * preprocess_ebuild_env || \
14 /usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.4.5/temp/logging/other: No space left on device
15 * die "error processing environment"
16 /usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.4.5/temp/logging/other: No space left on device
17 *
18 /usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.4.5/temp/logging/other: No space left on device
19 * If you need support, post the output of 'emerge --info =sys-devel/gcc-4.4.5',
20 /usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.4.5/temp/logging/other: No space left on device
21 * the complete build log and the output of 'emerge -pqv =sys-devel/gcc-4.4.5'.
22 /usr/lib/portage/bin/isolated-functions.sh: line 211: /var/tmp/portage/sys-devel/gcc-4.4.5/.die_hooks: No space left on device
23 /usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.4.5/temp/logging/other: No space left on device
24 * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.4.5/temp/build.log'.
25 /usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.4.5/temp/logging/other: No space left on device
26 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.4.5/temp/environment'.
27 /usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.4.5/temp/logging/other: No space left on device
28 * S: '/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5'
29 Traceback (most recent call last):
30 File "/usr/lib/portage/bin/ebuild-ipc.py", line 250, in <module>
31 sys.exit(ebuild_ipc_main(sys.argv[1:]))
32 File "/usr/lib/portage/bin/ebuild-ipc.py", line 247, in ebuild_ipc_main
33 return ebuild_ipc.communicate(args)
34 File "/usr/lib/portage/bin/ebuild-ipc.py", line 63, in communicate
35 lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True)
36 File "/usr/lib/portage/pym/portage/locks.py", line 72, in lockfile
37 myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660)
38 File "/usr/lib/portage/pym/portage/__init__.py", line 226, in __call__
39 rval = self._func(*wrapped_args, **wrapped_kwargs)
40 OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-devel/gcc-4.4.5/.ipc_lock'
41 * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
42 * behavior is known to be triggered by things such as failed variable
43 * assignments (bug #190128) or bad substitution errors (bug #200313).
44 * Normally, before exiting, bash should have displayed an error message
45 * above. If bash did not produce an error message above, it's possible
46 * that the ebuild has called `exit` when it should have called `die`
47 * instead. This behavior may also be triggered by a corrupt bash binary or
48 * a hardware problem such as memory or cpu malfunction. If the problem is
49 * not reproducible or it appears to occur randomly, then it is likely to
50 * be triggered by a hardware problem. If you suspect a hardware problem
51 * then you should try some basic hardware diagnostics such as memtest.
52 * Please do not report this as a bug unless it is consistently
53 * reproducible and you are sure that your bash binary and hardware are
54 * functioning properly.
55
56 * Messages for package sys-libs/timezone-data-2011h merged to /tmp/stage1root/:
57
58 * You do not have TIMEZONE set in /tmp/stage1root/etc/timezone.
59 * Setting /tmp/stage1root/etc/localtime to Factory.
60
61 * Messages for package net-misc/wget-1.12-r3 merged to /tmp/stage1root/:
62 * The /etc/wget/wgetrc file has been relocated to /etc/wgetrc
63
64
65 * Messages for package sys-apps/coreutils-8.7 merged to /tmp/stage1root/:
66 * Make sure you run 'hash -r' in your active shells.
67 * You should also re-source your shell settings for LS_COLORS
68 * changes, such as: source /etc/profile
69
70
71 * Messages for package sys-devel/gcc-4.4.5 merged to /tmp/stage1root/:
72 * The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
73 * is known to be triggered by things such as failed variable assignments
74 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
75 * exiting, bash should have displayed an error message above. If bash did
76 * not produce an error message above, it's possible that the ebuild has
77 * called `exit` when it should have called `die` instead. This behavior
78 * may also be triggered by a corrupt bash binary or a hardware problem
79 * such as memory or cpu malfunction. If the problem is not reproducible or
80 * it appears to occur randomly, then it is likely to be triggered by a
81 * hardware problem. If you suspect a hardware problem then you should try
82 * some basic hardware diagnostics such as memtest. Please do not report
83 * this as a bug unless it is consistently reproducible and you are sure
84 * that your bash binary and hardware are functioning properly.
85
86 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
87 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
88 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
89 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
90 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
91 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
92 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
93 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
94 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
95 umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011/tmp/kerncache: not mounted
96 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
97
98 !!! catalyst: run script failed.
99
100
101 Traceback (most recent call last):
102 File "modules/generic_stage_target.py", line 1207, in run_local
103 "run script failed.",env=self.env)
104 File "/usr/lib/catalyst/modules/catalyst_support.py", line 542, in cmd
105 raise CatalystError,myexc
106 CatalystError
107 None
108
109 !!! catalyst: Stage build aborting due to error.
110
111 /proc is still mounted; performing auto-bind-umount... !!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011//tmp/kerncache failed.
112 !!! catalyst: Killing any pids still running in the chroot
113 Checking for processes running in chroot and killing them.
114 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
115 umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011/tmp/kerncache: not mounted
116 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
117 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
118 umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011/tmp/stage1root/proc: not mounted
119 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
120 !!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011//tmp/kerncache
121 !!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011//tmp/stage1root/proc failed.
122 !!! catalyst: Killing any pids still running in the chroot
123 Checking for processes running in chroot and killing them.
124 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
125 umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011/tmp/stage1root/proc: not mounted
126 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
127 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
128 umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011/dev/pts: not mounted
129 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
130 !!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011//tmp/stage1root/proc
131 !!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011//dev/pts failed.
132 !!! catalyst: Killing any pids still running in the chroot
133 Checking for processes running in chroot and killing them.
134 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
135 umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011/dev/pts: not mounted
136 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
137 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
138 umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011/usr/portage: not mounted
139 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
140 !!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011//dev/pts
141 !!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011//usr/portage failed.
142 !!! catalyst: Killing any pids still running in the chroot
143 Checking for processes running in chroot and killing them.
144 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
145 umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011/usr/portage: not mounted
146 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
147 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
148 umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011/dev: not mounted
149 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
150 !!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011//usr/portage
151 !!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011//dev failed.
152 !!! catalyst: Killing any pids still running in the chroot
153 Checking for processes running in chroot and killing them.
154 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
155 umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011/dev: not mounted
156 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
157 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
158 umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011/proc: not mounted
159 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
160 !!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011//dev
161 !!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011//proc failed.
162 !!! catalyst: Killing any pids still running in the chroot
163 Checking for processes running in chroot and killing them.
164 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
165 umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011/proc: not mounted
166 cannot open /etc/mtab.tmp (No space left on device) - mtab not updated
167 !!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/stage1-ia64-20111011//proc
168
169 Traceback (most recent call last):
170 File "modules/generic_stage_target.py", line 1263, in run
171 apply(getattr(self,x))
172 File "modules/generic_stage_target.py", line 1212, in run_local
173 raise CatalystError,"Stage build aborting due to error."
174 CatalystError
175 None
176
177 !!! catalyst: Couldn't umount one or more bind-mounts; aborting for safety.
178
179
180 Traceback (most recent call last):
181 File "modules/generic_stage_target.py", line 609, in mount_safety_check
182 self.unbind()
183 File "modules/generic_stage_target.py", line 936, in unbind
184 "Couldn't umount one or more bind-mounts; aborting for safety."
185 CatalystError
186 None
187
188 !!! catalyst: Unable to auto-unbind /proc
189
190 Traceback (most recent call last):
191 File "/usr/lib/catalyst/catalyst", line 209, in build_target
192 mytarget.run()
193 File "modules/generic_stage_target.py", line 1265, in run
194 self.mount_safety_check()
195 File "modules/generic_stage_target.py", line 615, in mount_safety_check
196 raise CatalystError, "Unable to auto-unbind "+x
197 CatalystError
198 !!! catalyst: Error encountered during run of target stage1
199 Catalyst aborting....
200 lockfile does not exist '/var/tmp/catalyst/tmp/default/stage1-ia64-20111011/.catalyst_lock'
201
202
203
204 Full build log at /tmp/catalyst-auto.10712/log/stage1.log