Hi Frank, On 14/11/06 at 15:34 +0100, Frank Küster wrote: > Hm, thinking about this again: > > Frank Küster <[EMAIL PROTECTED]> wrote: > > > Lucas Nussbaum <[EMAIL PROTECTED]> wrote: > > > >> While doing archive rebuilds to prepare the etch release, I tried to > >> rebuild your package many times, but never succeeded. It always times > >> out at various steps, even after setting the timeout value to 90 min, > >> which is already huge since I build on quite fast bi-opterons. > > > > It takes more than 6 hours on my Mobile Pentium (Intel(R) Pentium(R) M > > processor 1.86GHz stepping 08), and one time it wasn't finished after 10 > > hours where I had to use the CPU time for something else and stopped it. > > You are just to impatient ;-) > > > >> If such long time without output are normal, would it possible to add a > >> option to some program so that it actually outputs something ? > > > > Hm. > > Maybe it wasn't clear to me what "time out" means in your setup. Does > it mean that it did not have *any* visible activity, like harddisk > access, in 90minutes? This is unexpected. The really long commands are > these:
sbuild checks for output to stdout. It means that during 90min, there was no output to stdout. > # Create Unicode encoded subfonts `$(uninamestem)00' .. > `$(uninamestem)ff'. > # This will take more than an hour. Make yourself a cup of tea. > @echo fontforge -script subfonts.pe $(typeface).ttf $(uninamestem) > $(sfddir)/Unicode.sfd > @( cd $(builddir) && fontforge -script subfonts.pe $(typeface).ttf > $(uninamestem) $(sfddir)/Unicode.sfd > log 2>&1 || ($(ERR)) ) > @echo > > and similar, all write their stdout to log. And I'd say there's one > message every couple of minutes usually. So if this didn't happen, > maybe this is more than a normal or wishlist bug... Maybe, then, they shouldn't output to the logfile. This would allow to see progress and please sbuild, too. > >> touch build-stamp.gkai > >> dh_testdir > >> touch build-stamp > >> Build killed with signal TERM after 90 minutes of inactivity > >> Build killed with signal KILL after 5 minutes of inactivity > >> Build killed with signal KILL after 5 minutes of inactivity > >> Build killed with signal KILL after 5 minutes of inactivity > > This looks as if a couple of processes timed out, where killed but the > build proceeded? Can you provide a full log? Yes, see http://http://ox.blop.info/bazaar/buildlogs/20061114/latex-cjk-chinese-arphic_1.15_etch32.buildlog -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
