On Mon, Feb 22, 2016 at 3:57 PM, Steven Chamberlain <ste...@pyro.eu.org> wrote: > Steven Chamberlain wrote: >> I used a messy sid chroot, maybe with some outdated or extra packages in >> there. I'll try again in a clean sid chroot. > > Done that, and I still *usually* get all tests pass on kfreebsd-amd64. > The buildd environment should be basically the same. Still, I can't reproduce the failure locally. Built zeromq3 about ten to twenty times with and without network access, on amd64 and i386 as well - always works here. My machine is old and dieing, this is the first time it behaves better than anything else.
> I get random failures about 1 time in 5, such as: > > | FAIL: test_security_curve > | ========================= > | > | lt-test_security_curve: tests/test_security_curve.cpp:140: int main(): > Assertion `rc == 0' failed. > | FAIL test_security_curve (exit status: 134) Strange that it's being run on your machine; disable-test_security_curve.patch disables this unconditionally. :-0 > | FAIL: test_inproc_connect > | ========================= > | > | Assertion failed: state == active || state == waiting_for_delimiter > (src/pipe.cpp:473) > | FAIL test_inproc_connect (exit status: 134) > > >> I think you need to `cat ./test-suite.log` or export TEST_VERBOSE=1 I don't see any difference even with passing VERBOSE=1 to dh_auto_test; can the reason be that it doesn't fail here? Which should be used? I don't see it mentioned in the docs. > Please see the attached, it will show the reason for test failures in > the build log, which should help figure out what is wrong on Linux. First, may you test the proposed package update[1]? I've to guard the ucred.h inclusion as that's kFreeBSD only. Cheers, Laszlo/GCS [1] dget -x http://www.barcikacomp.hu/gcs/zeromq3_4.1.4-4.dsc
