control: forwarded -1 https://github.com/jvirkki/libbloom/issues/7 control: severity -1 important
On Tue, 16 May 2017 22:34:42 +0300 Adrian Bunk <b...@debian.org> wrote: > Source: libbloom > Version: 1.4-6 > Severity: serious > > https://buildd.debian.org/status/fetch.php?pkg=libbloom&arch=amd64&ver=1.4-6&stamp=1494930635&raw=0 > > ... > /«PKGBUILDDIR»/build/test-libbloom > ----- Running basic tests ----- > ----- basic ----- > bloom at 0x7ffc4a988c30 not initialized! > bloom at 0x7ffc4a988c30 not initialized! > bloom at 0x7ffc4a988c30 > ->entries = 102 > ->error = 0.100000 > ->bits = 488 > ->bits per elem = 4.792529 > ->bytes = 61 > ->hash functions = 4 > ----- add_random(10, 0.100000, 10, 0, 1, 32, 1) ----- > bloom at 0x7ffc4a988b20 > ->entries = 10 > ->error = 0.100000 > ->bits = 47 > ->bits per elem = 4.792529 > ->bytes = 6 > ->hash functions = 4 > entries: 10, error: 0.100000, count: 10, coll: 2, error: 0.200000, bytes: 6 > error: expected error 0.100000 but observed 0.200000 > Makefile:124: recipe for target 'test' failed > make[2]: *** [test] Error 1 Thanks for the report! Considering that: - The build actually suceeded, but failed at unit test. - the unit test fails at low rate. Recent releases only changed Makefile and intended to fix FTBFS issue on kFreeBSD and Hurd. It doesn't affect amd64. Previous amd64 was built OK, and all other ARCHs are all built OK on latest release. - If restart the amd64, it should build OK. Actually I ever built on DoM: http://debomatic-amd64.debian.net/distribution#unstable/libbloom/1.4-6/buildlog So lower the severity. I already raised this unit test issues upstream. Hope upstream can give a clue on this. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
pgpE2O0wk1lUd.pgp
Description: PGP signature
