12 Dec
2018
12 Dec
'18
10:54 a.m.
I see sporadic segfaults during jenkins builds every now and then...
Let's keep an eye on it.
This one built on build2-deb9build-ansible
~N
On Wed, Dec 12, 2018 at 12:52:59AM +0000, jenkins(a)lists.osmocom.org wrote:
See
<https://jenkins.osmocom.org/jenkins/job/master-osmo-msc/IU=--enable-iu,WITH_MANUALS=0,a3=default,a4=default,label=osmocom-master-debian9/7408/display/redirect>
...
CC auth_milenage.lo
/bin/bash: line 2: 6091 Segmentation fault (core dumped) /bin/bash ../../libtool
--silent --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include
-I../../include -I/usr/include/p11-kit-1 -DBUILDING_LIBOSMOCORE -Wall -Wall -g -O2
-DBUILDING_LIBOSMOCORE -Wall -MT auth_milenage.lo -MD -MP -MF $depbase.Tpo -c -o
auth_milenage.lo auth_milenage.c
make[3]: *** [auth_milenage.lo] Error 139
Makefile:582: recipe for target 'auth_milenage.lo' failed
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/build/deps/libosmocore/src/gsm'
12 Dec
12 Dec
12:26 p.m.
There's no much we can do about that other than opening an OBS bug
report. It's a segfault in either bash or libtool, so not related to us.
It could be a bug in bash/libtool or even on the virtualization layer
being used by OBS to run containers.
Regards,
Pau
--
- Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
4:10 p.m.
On Wed, Dec 12, 2018 at 01:26:45PM +0100, Pau Espin Pedrol wrote:
on the virtualization layer being used by OBS to run
containers.
This is our own jenkins build slave, not an OBS package builder.
In our build slaves, sporadic failures usually didn't happen. Might hint at
faulty RAM or somesuch. Or just a flapping bug, of course.
~N
9:13 p.m.
On Wed, Dec 12, 2018 at 05:10:17PM +0100, Neels Hofmeyr wrote:
On Wed, Dec 12, 2018 at 01:26:45PM +0100, Pau Espin
Pedrol wrote:
might be useful to look at whether it happens on one particular build slave
only, or on multiple/all. If it's only one particular machine, then very clearly
that machine is likely broken.
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
on the virtualization layer being used by OBS to
run containers.
This is our own jenkins build slave, not an OBS package builder. 
2:29 p.m.
Hit this recently as well with
https://jenkins.osmocom.org/jenkins/job/gerrit-libosmocore/1319/a2=default,…
Is there way to retrieve core dump to see what exactly went wrong?
What're the settings for |systemd-coredump on buildhost?
|
12.12.18 11:54, Neels Hofmeyr пишет:
I see sporadic segfaults during jenkins builds every
now and then...
Let's keep an eye on it.
This one built on build2-deb9build-ansible
~N
--
- Max Suraev <msuraev(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Directors: Harald Welte
2425
days inactive
2425
days old
4 comments
4 participants
participants (4)
-
Harald Welte -
Max -
Neels Hofmeyr -
Pau Espin Pedrol