Bug#487375: pypy: FTBFS: Keeps running.
Package: pypy Version: 1.0.0-svn55443-1 Severity: serious Hi, Your package is failing to build with the following error: [c] 26 nodes [ array: 39749 boehm rtti: 748 func: 8864 struct: 212954 ] [c] 261000 nodes [ array: 39807 boehm rtti: 751 func: 8880 struct: 213220 ] make[1]: *** [bin/pypy] Terminated make: *** [build-arch-stamp] Terminated Build killed with signal 15 after 150 minutes of inactivity This means it didn't output anything for 150 minutes, and probably hanged doing something. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487375: pypy: FTBFS: Keeps running.
Hi, Your package is failing to build with the following error: [...] Build killed with signal 15 after 150 minutes of inactivity I can't seem to reproduce that here, but it is happening on a few architectures according to buildd.d.o. (Out of interest, what arch were you building on?) Could you confirm you aren't running out of memory or disk space during the build? The translation process can take a *large* amount of physical memory: previous tests show that on systems with less than ~1GB of memory the translation process causes heavy disk thrashing and takes literally days to complete (which is what you might be seeing). However, if you reply in the negative, I'll wait a few days and see if in a a new upstream snapshot makes these problems just go away (not particulary a great practice, but this package should probably be in experimental, tbh). Regards, -- Chris Lamb, UK [EMAIL PROTECTED] GPG: 0x634F9A20 signature.asc Description: PGP signature
Bug#487375: pypy: FTBFS: Keeps running.
On Sat, Jun 21, 2008 at 06:34:28PM +0100, Chris Lamb wrote: Hi, Your package is failing to build with the following error: [...] Build killed with signal 15 after 150 minutes of inactivity I can't seem to reproduce that here, but it is happening on a few architectures according to buildd.d.o. (Out of interest, what arch were you building on?) This was on an amd64. Could you confirm you aren't running out of memory or disk space during the build? The translation process can take a *large* amount of physical memory: previous tests show that on systems with less than ~1GB of memory the translation process causes heavy disk thrashing and takes literally days to complete (which is what you might be seeing). I have no idea how much RAM that buildd it was running on has, but I think it has 4G. I've just started it on the other for which I know it has 2G of RAM. We'll see what happens. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487375: pypy: FTBFS: Keeps running.
On Sat, Jun 21, 2008 at 07:59:34PM +0200, Kurt Roeckx wrote: Could you confirm you aren't running out of memory or disk space during the build? The translation process can take a *large* amount of physical memory: previous tests show that on systems with less than ~1GB of memory the translation process causes heavy disk thrashing and takes literally days to complete (which is what you might be seeing). I have no idea how much RAM that buildd it was running on has, but I think it has 4G. I've just started it on the other for which I know it has 2G of RAM. We'll see what happens. So it worked now. It was atleast using 1.3 GB of RAM somewhere during the build proces. It also took 2 hours now. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487375: pypy: FTBFS: Keeps running.
Kurt Roeckx wrote: So it worked now. It was atleast using 1.3 GB of RAM somewhere during the build proces. Hm, okay. I will bump the built-in warning to this level. It also took 2 hours now. This is normal! :) Not sure how to proceed now to be honest; I think I will still update to a new SVN snapshot in a few days. Regards, -- Chris Lamb, UK [EMAIL PROTECTED] GPG: 0x634F9A20 signature.asc Description: PGP signature
