Hi Santiago, On 29-11-16 22:22, Santiago Vila wrote: >> Do you think it may help to disable parallelism? > > Do you mean, for the purposes of reproducing the error, or for the > purposes of avoiding it? :-)
I meant for the purpose of avoiding that.
> $ENV{'DEB_BUILD_OPTIONS'} = 'parallel=1';
I saw that after my e-mail. So at least that doesn't help.
I ran a couple of builds on debomatic, and unfortunately for this bug,
it doesn't trigger the hang there. What is the ratio (approximately of
course) of hangs versus no hangs?
Luckily, the hangs (when they happen) are always on the same location
and I now have some ideas of debugging (how difficult is it for you to
try my first idea?)
The issue is always with introspection. Due to bug 839397¹ I added a
work-around to liferea. That bug is fixed, so the work-around isn't
needed anymore. Do the hangs also occur when line 13 in the debian/rules
file that contains
"export WEBKIT_DISABLE_COMPOSITING_MODE=1"
is disabled?
The other idea to try is to run the introspection command manually on
both a liferea binary from a successful build (in a loop) and from a
failed build (if you/we can extract that somehow): "g-ir-scanner
liferea". All of this of course in a similar environment where the hang
occurs. It that is the case, I guess it is easier to really debug the
issue, because I assume we could than run g-ir-scanner under gdb and
inspect it when it hangs.
I'll play around a bit in my build environments (pbuilder) to see if I
can learn something there when I have time.
Anyways, it is my suspicion that this bug should be reassigned to some
introspection package, but we need to figure out which one.
Paul
¹ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839397
signature.asc
Description: OpenPGP digital signature
