Date: Tue, 13 Oct 2015 21:44:13 -0700 From: Bryan Drewery <bryan-lists@shatow.net> To: freebsd-current@freebsd.org Subject: Re: FreeBSD_HEAD_amd64_gcc4.9 - Build #652 - Failure Message-ID: <561DDD9D.8060505@shatow.net> In-Reply-To: <561D80F4.8090502@shatow.net> References: <346597700.1.1444719969115.JavaMail.jenkins@jenkins-9.freebsd.org> <CAG=rPVc95bMV5kx6FJNyfn35Gs3nyFZ%2BAoNiRTTB1AvYSeYepg@mail.gmail.com> <561D80F4.8090502@shatow.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/13/2015 3:08 PM, Bryan Drewery wrote: > On 10/13/2015 12:24 PM, Craig Rodrigues wrote: >> On Tue, Oct 13, 2015 at 12:05 AM, <jenkins-admin@freebsd.org> wrote: >> >>> --- env_test --- >>> /usr/local/bin/x86_64-portbld-freebsd10.1-g++ -isystem >>> /builds/FreeBSD_HEAD_amd64_gcc4.9/obj/builds/FreeBSD_HEAD_amd64_gcc4.9/tmp/usr/include >>> -L/builds/FreeBSD_HEAD_amd64_gcc4.9/obj/builds/FreeBSD_HEAD_amd64_gcc4.9/tmp/usr/lib >>> --sysroot=/builds/FreeBSD_HEAD_amd64_gcc4.9/obj/builds/FreeBSD_HEAD_amd64_gcc4.9/tmp >>> -B/usr/local/x86_64-freebsd/bin/ >>> -I/builds/FreeBSD_HEAD_amd64_gcc4.9/obj/builds/FreeBSD_HEAD_amd64_gcc4.9/tmp/usr/include/c++/v1 >>> -std=gnu++11 >>> -L/builds/FreeBSD_HEAD_amd64_gcc4.9/obj/builds/FreeBSD_HEAD_amd64_gcc4.9/tmp/../lib/libc++ >>> --sysroot=/builds/FreeBSD_HEAD_amd64_gcc4.9/obj/builds/FreeBSD_HEAD_amd64_gcc4.9/tmp >>> -B/usr/local/x86_64-freebsd/bin/ -O2 -pipe -DHAVE_CONFIG_H >>> -DATF_C_TESTS_BASE='"/usr/tests/lib/atf/libatf-c"' >>> -DATF_INCLUDEDIR='"/usr/include"' >>> -I/builds/FreeBSD_HEAD_amd64_gcc4.9/contrib/atf -fstack-protector-strong >>> -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter >>> -Wpointer-arith -Wno-uninitialized -o env_test env_test.o test_helpers.o >>> -lprivateatf-c++ -lprivateatf-c -lprivateatf-c >>> test_helpers.o: file not recognized: File truncated >>> >> >> >> I think that there is a race condition in >> src//lib/atf/libatf-c++/tests/detail/Makefile , >> where if built with parallel jobs ( -j ), once in a while, test_helpers.o >> is not fully built >> before another job tries to link it. This doesn't fail all the time, but >> fails intermittently, >> which makes it hard to spot. >> > > It looks like a bsd.progs.mk issue. I'll look more. > > r289286 will handle this and similar cases. Hopefully this holds. -- Regards, Bryan Drewery bdrewery@freenode/EFNet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?561DDD9D.8060505>