On 10/10/12 03:20, Scott Kitterman wrote: >> Christoph Egger tried to build it locally to collect >> unit_tests/test-suite.log so we could understand why it failed. [...] > Someone did something and it's built now, so nevermind/thank you as > appropriate.
Hi Scott, I guess it was given back for rebuild and just worked this time. The unit_tests/test-suite.log seems to be echoed out in the build log already, _above_ the message saying "See unit_tests/test-suite.log". (The part beginning "ClamAV 0.97.6: unit_tests/test-suite.log", is only present in the buildd logs where a test failed). So the "1 of 7 tests" that failed seems to be these timeouts, at a different place in each of the build attempts; maybe it doesn't allow enough time, or otherwise it could be a thread-related hang (these have been seen before with kFreeBSD's eglibc in some rare cases) : > FAIL: check_clamav (exit: 1) > ============================ > > Running suite(s): cl_api > cli > jsnorm > str > regex > disasm > unique > matchers > htmlnorm > bytecode > 99%: Checks: 320, Failures: 1, Errors: 1 > check_htmlnorm.c:126:E:htmlnorm api:test_htmlnorm_api:4: (after this point) > Test timeout expired > FAIL: check_clamav (exit: 1) > ============================ > > Running suite(s): cl_api > cli > jsnorm > str > regex > disasm > unique > matchers > htmlnorm > bytecode > 99%: Checks: 320, Failures: 0, Errors: 2 > check_regex.c:409:E:phishingScan with 2 dbs:phishingScan_test:27: (after this > point) Test timeout expired > check_regex.c:384:E:phishingScan with 2 dbs:phishing_fake_test:0: (after this > point) Test timeout expired Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50755c9c.5050...@pyro.eu.org
