Bug#880883: FTBFS on arm64: test suite times out (on arm-arm-04)

[Emilio Pozuelo Monfort]

On 12/11/17 15:02, Michael Biebl wrote:
> Am 05.11.2017 um 13:14 schrieb Michael Biebl:
>> Looking through past build logs, it consistently seems to fail at this
>> point:
>>
>> make[7]: Entering directory
>> '/<<PKGBUILDDIR>>/debian/build/deb/tests/refcount'
>> make     closures objects objects2 properties properties2 properties3
>> properties4 signal1 signal2 signal3 signal4  \
>>
> 
> ..
> 
>> make[8]: Leaving directory
>> '/<<PKGBUILDDIR>>/debian/build/deb/tests/refcount'
>> make  check-TESTS check-local
>> make[8]: Entering directory
>> '/<<PKGBUILDDIR>>/debian/build/deb/tests/refcount'
>> make[9]: Entering directory
>> '/<<PKGBUILDDIR>>/debian/build/deb/tests/refcount'
>> E: Build killed with signal TERM after 150 minutes of inactivity
> I'm not sure if the arm porters already had time to look into this. But
> since a week has passed without further feedback and glib2.0 starting to
> block other packages, this is another plea for help from the arm porters
> regarding this issue.

I gave it back again, and it again got picked by arm-arm-04. With the help from
jcristau (as I don't have access to that machine) I determined that the build
gets killed while running the closures test, which gets executed by is way too
slow on that machine (it'd take around 200 minutes to complete it).

I'm not sure where it's taking so much time on this machine (can't know without
access or some debugging logs) but I wonder if it's on g_closure_ref/unref,
which happen quite a lot. Maybe atomic operations are too slow on this hardware?

Cheers,
Emilio