Re: Bug#858095: atlc FTBFS on mips: Build killed with signal TERM after 360 minutes of inactivity

James Cowgill <[email protected]>
Newsgroups gmane.linux.debian.ports.mips
Message-ID <[email protected]>
Hi,

On 19/03/17 14:11, Adrian Bunk wrote:
> On Sun, Mar 19, 2017 at 07:28:47AM -0600, Bdale Garbee wrote:
>> Adrian Bunk <[email protected]> writes:
>>
>>> Now one test is taking over 6 hours (is that completely hanging?).
>>
>> I have no idea.  Never seen that happen.  Makes me wonder what's changed
>> in your kernel or toolchain since the last build?
> 
> Nothing of this is "mine", this is a build failure seen on the
> Debian buildds:
>   https://buildd.debian.org/status/logs.php?pkg=atlc&arch=mips
> 
> The latest successful build was in 2011 using gcc 4.6 on a machine 
> running kernel 2.6.32
> 
> The failing attempts are with gcc 6 and kernel 3.16

After a few attempts atlc built again. This is probably caused by the
MIPS builders which do not have an FPU. To do floating point they have
to trap into the kernel which is very slow.

James
signature.asc (application/pgp-signature, 819 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJY0P+JAAoJEMfxZ23qLQHvTZYQAKpauAZ06HXtXtnfdVtV4SEj
J1ooPBgyvrRTIf4rbR1J5LFS57RPcyuD6lfRSJEnjuFUS0E/qOH07n3THcKtbj/U
klt5DfD1hRsvrPfFyiSR5fjkJyNwskugAR2kIeLvQJcSGbKY/3Sbp7otERD2mw1L
ByE1r6TQSKxYmq31/SgEzG34JCxlkWhP5gRQI740rdtgVZbKuUwC6Gp+pZjYMI3i
gvU9xh1L7o65Jfi7gYrbsRBqwRP0R6pfiAnxZMHPutBpeT74C9ghTPKNd2HCwdTX
oPRAGBi79X25bCq5jyCeOywiiFJNGv7gR9C/IHKXlgzANQdqijy9aCnzXhXn9spt
WFVKzTfMiwqgJ5rYBFRrsq0ymUL04yyB2tEBrdNimOX9Q3+yGRf7lZRjMr/fP7TG
Ts15xiT3P79mrXeJNYn+Bp4oxcrnnj6QodRWgzNV6J65WY8bt64F/A7m1f2yx1US
nysSER+nJvP1EEuh+e/TTaep9kgss9i8I9bREX0s3u94PNmybdCfoFDBnGEyM0Pc
NSy8bzg2L4UBsISdbs+rkLOeixpCX9ZqJTJTnXV42tLQRwgwxO09HMzk/A58e/H5
PHyDYfEEcNiXwxlxpCO5/+9w9oWhlUAK/rCEaP8gThWreFGfXv4haiyJGUalnoQL
8ew/Nz7MTMYBfoE0vpFQ
=w9Eu
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.