We didn't follow up on this unfortunately but latter builds in other
releases as well as xenial work fine.
For example:
https://launchpad.net/ubuntu/+source/strongswan/5.3.5-1ubuntu3.3
** Changed in: strongswan (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug
It still hangs on my laptop, but in a schroot so harder than usual to debug.
I'll keep it til tomorrow morning, if you let me know anything else I should
check there let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just hit that today.
FYI
#0 0x7f22d25008a8 in __pthread_mutex_cond_lock_full (mutex=0xca) at
../nptl/pthread_mutex_lock.c:409
#1 0x7f22d2747970 in ?? ()
#2 0x564037d2bae0 in frame_dummy ()
#3 0x564037d2bb7d in test_runner_init (init=init@entry=false) at tests.c:55
#4
I've seen this in some Travis CI runs of our test suite. There
occasionally seems to be a lockup (not sure if it is an actual
deadlock). But I was never able to reproduce it. Is it possible to get a
backtrace when the test hangs and gets killed by the builder? Or logon
to the build host and attach
several retries always show the same error. Can't reproduce locally in a
fresh chroot using the following configurations:
- xenial-release
- xenial-release + -updates + -security
- xenial-release + ppa:ubuntu-toolchain-r/ppa
- xenial-release + -updates + -security + ppa:ubuntu-toolchain-r/ppa
