Mailinglist Archive: opensuse-buildservice (80 mails)

< Previous Next >
Re: [opensuse-buildservice] nodejs10 build failures
On Dienstag, 21. August 2018, 23:06:44 CEST wrote Hans-Peter Jansen:
Hi Adrian,

thanks for your support.

On Dienstag, 21. August 2018 16:18:05 Adrian Schröter wrote:
On Dienstag, 21. August 2018, 16:09:59 CEST wrote Hans-Peter Jansen:
On Montag, 20. August 2018 19:27:07 Hans-Peter Jansen wrote:

today, I stumbled across strange build failures of nodejs10:

Most failed builds stopped at some point during install without further
indication why exactly. It looks like some watchdog is chiming in and
stopping the builder. Are there some _constraints missing? 40G disk
more than enough to me, even if additional intree packages are being

Any idea, what's going on here?

Here are some recurring failure patterns for consecutive builds:

After outputting a *huge* link command:
Note the printf: write error and how output is truncated here.

eps/openssl/openssl/crypto [ 1712s] printf: write error
[ 1712s] deps/openssl/ recipe for target
nssl/libopenssl.a' failed [ 1712s] make[1]: ***
nssl/libopenssl.a] Error 1 [ 1712s] make[1]: *** Waiting for unfinished
[ 1725s] rm fbd2db1fc4431e5fd3695925235da4a90ab137a7.intermediate
8d9c811780d88c5f90f85246b1cdc5cff28496d2.intermediate [ 1725s]
Makefile:87: recipe for target 'node10' failed
[ 1725s] make: *** [node10] Error 2
[ 1725s] error: Bad exit status from /var/tmp/rpm-tmp.bdntvC (%install)

Here, it is failing out of the blue without any further indication:

[ 2255s] installing
64/node_modules/npm10/node_modules/lodash.union/ [ 2255s]
64/node_modules/npm10/node_modules/lodash.union/LICENSE [ 2255s]
installing /home/abuild/rpmbuild/BUILDROOT/nodejs10error: Bad exit status
from /var/tmp/rpm-tmp.13cfRU (%install) [ 2255s]
[ 2255s]
[ 2255s] RPM build errors:
[ 2255s] Bad exit status from /var/tmp/rpm-tmp.13cfRU (%install)
[ 2255s]
[ 2255s] cumulus3 failed "build nodejs10.spec" at Tue Aug 21 10:07:45 UTC

Write error of a file:

8d9c811780d88c5f90f85246b1cdc5cff28496d2.intermediate [ 2131s] make[1]:
write error
[ 2131s] Makefile:87: recipe for target 'node10' failed
[ 2131s] make: *** [node10] Error 1
[ 2131s] error: Bad exit status from /var/tmp/rpm-tmp.Vsmbi1 (%install)
[ 2131s]
[ 2131s]
[ 2131s] RPM build errors:
[ 2131s] Bad exit status from /var/tmp/rpm-tmp.Vsmbi1 (%install)
[ 2131s]
[ 2131s] cumulus2 failed "build nodejs10.spec" at Tue Aug 21 10:19:37 UTC

These failures are for different targets, that differ in amount of 3rd
party packages, that are included in the build. The failures are somewhat
similar, but without a recognizable pattern.

A build for 15.0 includes the lowest number of those intree 3rd party
packages, and seems to have the highest chance for a successful build,
but even that build fails more often than not. :-(

OTOH, local builds succeed every time.

Any idea, what's going on here, is much appreciated.

You have tried kvm local builds? Because this is usually the main

osc build --vm-type=kvm ...


Yes, it fails, but with different patterns.

What can make (even local) kvm builds so touchy?

well, the difference between chroot and kvm builds are

* own distro specific kernel (less likely the reason here, since multiple
targets are affected)
* no network access (less likely since you said it can work)
* reduced memory and storage. You have already large memory setting,
so disk-full is next to check. You can also check the _statistics file
of a successful build. It can tell you what amount of storage was used.
But this makes only sense if you have one of this source revision

Btw, I have branched an a bit older source of nodejs10 yesterday, since someone
claimed it is the fault of latestet OBS deployment. Of course the older
source revision still builds ;)
(home:adrianSuSE:branches:devel:languages:nodejs nodejs10)

So the change which most likely broke it was the update to nodejs 10.9.0 in

osc rdiff -c23 devel:languages:nodejs nodejs10

however, this does not help you most likely, since you want to get the new
version building.

For one I would mount the root fs of your local build VM with the failure.
Run "df" on it to see if it is the disk full issue.

In case it isn't, you need to get some better debug information. First
dumb attempt would be to run the make install via strace.


Adrian Schroeter
email: adrian@xxxxxxx

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284
(AG Nürnberg)

Maxfeldstraße 5
90409 Nürnberg

To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >