Re: Please retry failed pypy builds on i386 and armel
On Mon, Dec 02, 2013 at 08:25:33PM +0200, Stefano Rivera wrote: Hi Kurt (2013.12.01_14:44:20_+0200) I gave it back, we'll see what happens. Great, same failure on i386 :/ I tried locally (twice), and it built without issue. Retry again? I could also upload one of my builds, but I'd prefer it to build on a buildd. Given back again. Kurt -- To UNSUBSCRIBE, email to debian-wb-team-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131203120927.ga2...@roeckx.be
Re: Please retry failed pypy builds on i386 and armel
Hi Kurt (2013.12.01_14:44:20_+0200) I gave it back, we'll see what happens. Great, same failure on i386 :/ I tried locally (twice), and it built without issue. Retry again? I could also upload one of my builds, but I'd prefer it to build on a buildd. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 461 1230 C: +27 72 419 8559 -- To UNSUBSCRIBE, email to debian-wb-team-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131202182533.gz3...@bach.rivera.co.za
Re: Please retry failed pypy builds on i386 and armel
Hello, 2013/11/30 Stefano Rivera stefa...@debian.org: PyPy usually builds on i386 (without any trouble) and armel (fairly slowly). The lastest upload timed out on both. We should retry (and possibly raise the timeouts a bit). gb pypy_2.2.1+dfsg-1 . i386 armel On armel: E: Caught signal ‘Terminated’: terminating immediately Build killed with signal TERM after 600 minutes of inactivity It is already increased. Thanks, SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 461 1230 C: +27 72 419 8559 -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-. -- To UNSUBSCRIBE, email to debian-wb-team-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caodfweemcsspywubotstyqzlqo66kyrrymldev9+hykonuj...@mail.gmail.com
Re: Please retry failed pypy builds on i386 and armel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Hector (2013.12.01_03:56:26_+0200) 2013/11/30 Stefano Rivera stefa...@debian.org: PyPy usually builds on i386 (without any trouble) and armel (fairly slowly). The lastest upload timed out on both. We should retry (and possibly raise the timeouts a bit). gb pypy_2.2.1+dfsg-1 . i386 armel On armel: E: Caught signal ‘Terminated’: terminating immediately Build killed with signal TERM after 600 minutes of inactivity It is already increased. And re-looking at the i386 timeout, it's something I've seen before - probably failing to clean up a subprocess, and never temininating. Unfortunately I've never figured that one out, it happens occasionally. Increasing the i386 timeout wouldn't help. SR - -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 461 1230 C: +27 72 419 8559 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Debian :: The Universal Operating System iQIcBAEBCgAGBQJSmpghAAoJEACQ/CG1zRrMwSkP/0xXl2sJ5nb2z9Z/EzYOaGrt VQ2Xq/A6llkaXae+b53N9qrqTZqJtgpRZTCMdLDdJbdZ3qzwCyn2wHP23G/zO6g2 svDzfMixyIze0hWaxMUzCnIiW9z4FSISXpqWNTy+uABLUNwhYuS1veSAlUKNUIlT Kph43Qy2cKrWfwKgOggVAMjnCkl/SSno/nqH3o2RKOyXXGUypdMxqoA0CRld8kmU ZxpjL5TSxt8Ouh+CMarpT9Ywc6P/DYTqV4+Tfiypcyxzy9BwZ9GJ6hweMurAd58j 9Jtk6ttDYDfjFu6IcSBX4uMUyNwRLyL66/XNP7g6LFWwokBUsvKTqnZWP510PaaE IIWnBzH7iaocpP/2xQ9vvPG5h6WFx/rPN7HLm5HiQ3DfBlKOhH52nU+ZJxEQandJ 0aM+Ky1zlc46jJYEoTeQtwOY2E/sB1UezOO++ieyWnsC1Kbc99TRavFu+V1Kt/1c lsSoP3QD3MHCXX0GWu/HhereQ1YoCdtMFJAkGbYLwCBa+KDKt1T8osUSJlKgLJf+ PKxFL7dMCOceFBXcoIB6xMnlrPmSmjwUnGFEr99qPFuucz+YapGNnMsfEw+Jg8Kx qOczQ4UKIMs3iE3qKhofVNYMjm2lrjtlswXGYqqcAYUFdU/i9iztA6U2wqkeARjn rGhZKMeCbbOW4McGKqwx =wnjc -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-wb-team-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131201020001.gw3...@bach.rivera.co.za
