Bug#860701: glm: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

Source: glm
Version: 0.9.8.3-2
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
>         Start  17: test-core_type_mat4x3
>  17/108 Test  #17: test-core_type_mat4x3 ..................   Passed    0.00 sec
>         Start  18: test-core_type_mat4x4
>  18/108 Test  #18: test-core_type_mat4x4 ..................   Passed    0.00 sec
>         Start  19: test-core_type_vec1
>  19/108 Test  #19: test-core_type_vec1 ....................   Passed    0.00 sec
>         Start  20: test-core_type_vec2
>  20/108 Test  #20: test-core_type_vec2 ....................   Passed    0.00 sec
>         Start  21: test-core_type_vec3
>  21/108 Test  #21: test-core_type_vec3 ....................   Passed    0.00 sec
>         Start  22: test-core_type_vec4
>  22/108 Test  #22: test-core_type_vec4 ....................   Passed    0.00 sec
>         Start  23: test-core_func_common
>  23/108 Test  #23: test-core_func_common ..................   Passed    0.00 sec
>         Start  24: test-core_func_exponential
> E: Build killed with signal TERM after 150 minutes of inactivity

The full build log is available from:
   http://aws-logs.debian.net/2017/04/18/glm_0.9.8.3-2_testing-i386.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.