Package: schroedinger Version: 1.0.9-4 Severity: important pk...@porpora:/home/buildd/logs$ ls -al schroedinger_1.0.9-4-powerpc-20101004-0714 -rw-r--r-- 1 buildd buildd 511938796 2010-10-04 07:20 schroedinger_1.0.9-4-powerpc-20101004-0714
Finished at 20101004-0720 Build needed 00:06:04, 28760k disc space I suspect most of the few minutes it needs to build it spends in flushing the build log to disk. We over at the wanna-build front do not support such huge logs. The log mainly contains of useless repetitive ANSI output like this (when viewed with less): ESC[00;32m 114ESC[00m ESC[00;32m 114ESC[00m ESC[00;32m 114ESC[00m ESC[00;32m 114ESC[00m ESC[00;32m 114ESC[00m ESC[00;32m 114ESC[00m ESC[00;32m 114ESC[00m ESC[00;32m 114ESC[00m ESC[00;32m 114ESC[00m ESC[00;32m 114ESC[00m ESC[00;32m 114ESC[00m ESC[00;32m 114ESC[00m ESC[00;32m 114ESC[00m ESC[00;32m 114ESC[00m ESC[00;32m 114ESC[00m ESC[00;32m 114ESC[00m ESC[00;32m 114ESC[00m ESC[00;32m 114ESC[00m ESC[00;32m 114ESC[00 m ESC[00;32m 114ESC[00m And there are numbers between those lines. I guess that's a test going havoc? It's happening here: SCHRO: ERROR: schromotion.c(112): schro_motion_init_functions: compile failed SCHRO: ERROR: schromotion.c(204): schro_motion_init_functions: compile failed SCHRO: ERROR: schromotion.c(112): schro_motion_init_functions: compile failed SCHRO: ERROR: schromotion.c(204): schro_motion_init_functions: compile failed PASS: encode Filter 0: forward test "random 0": ===== Is it actually putting out video into the build log? The build log in question will be deleted now, though, and can be regenerated on request. It's also not available at the usual places because it's too big to be sent by mail. Kind regards, Philipp Kern -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
