Date: Mon, 29 Aug 2016 10:54:04 -0700 From: Bryan Drewery <bdrewery@FreeBSD.org> To: Li-Wen Hsu <lwhsu@FreeBSD.org> Cc: Dimitry Andric <dim@FreeBSD.org>, Craig Rodrigues <rodrigc@freebsd.org>, "jenkins-admin@freebsd.org" <jenkins-admin@freebsd.org>, "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org>, jmmv@FreeBSD.org Subject: Re: Jenkins build is still unstable: FreeBSD_HEAD #564 Message-ID: <153107ba-094b-3eec-165b-a10080d6d26b@FreeBSD.org> In-Reply-To: <20160829175247.GA10263@FreeBSD.cs.nctu.edu.tw> References: <1491374121.44.1472440150670.JavaMail.jenkins@jenkins-9.freebsd.org> <166099893.51.1472451061454.JavaMail.jenkins@jenkins-9.freebsd.org> <CAG=rPVdZp171Egp=OHWDc3qCgcJDE3HQ0rv-j=i%2BO1LHcfH%2BJQ@mail.gmail.com> <CFA236ED-7DE0-4BE1-B944-52284E2FB6E0@FreeBSD.org> <6E443BB8-0269-4812-A2F4-40AA303E69C6@FreeBSD.org> <CAG=rPVdfgoF0mts-edHATUaefD7YuGtNu5ZTJOa8efUn2W4QuA@mail.gmail.com> <8058052E-A09A-403E-828A-74B51ED4BBF4@FreeBSD.org> <20160829163911.GA51650@FreeBSD.cs.nctu.edu.tw> <E73154DF-6A88-457D-B1FF-6B7F7610C37F@FreeBSD.org> <4b8980f0-1a90-40d7-45b3-9569b321d1c6@FreeBSD.org> <20160829175247.GA10263@FreeBSD.cs.nctu.edu.tw>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --8OcGBqASbmaScm8JfvKkt0X3kkQmCjLx6 Content-Type: multipart/mixed; boundary="w33HnxQv0JV2SiT38dt8ljc1pbpdVlKBD" From: Bryan Drewery <bdrewery@FreeBSD.org> To: Li-Wen Hsu <lwhsu@FreeBSD.org> Cc: Dimitry Andric <dim@FreeBSD.org>, Craig Rodrigues <rodrigc@freebsd.org>, "jenkins-admin@freebsd.org" <jenkins-admin@freebsd.org>, "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org>, jmmv@FreeBSD.org Message-ID: <153107ba-094b-3eec-165b-a10080d6d26b@FreeBSD.org> Subject: Re: Jenkins build is still unstable: FreeBSD_HEAD #564 References: <1491374121.44.1472440150670.JavaMail.jenkins@jenkins-9.freebsd.org> <166099893.51.1472451061454.JavaMail.jenkins@jenkins-9.freebsd.org> <CAG=rPVdZp171Egp=OHWDc3qCgcJDE3HQ0rv-j=i+O1LHcfH+JQ@mail.gmail.com> <CFA236ED-7DE0-4BE1-B944-52284E2FB6E0@FreeBSD.org> <6E443BB8-0269-4812-A2F4-40AA303E69C6@FreeBSD.org> <CAG=rPVdfgoF0mts-edHATUaefD7YuGtNu5ZTJOa8efUn2W4QuA@mail.gmail.com> <8058052E-A09A-403E-828A-74B51ED4BBF4@FreeBSD.org> <20160829163911.GA51650@FreeBSD.cs.nctu.edu.tw> <E73154DF-6A88-457D-B1FF-6B7F7610C37F@FreeBSD.org> <4b8980f0-1a90-40d7-45b3-9569b321d1c6@FreeBSD.org> <20160829175247.GA10263@FreeBSD.cs.nctu.edu.tw> In-Reply-To: <20160829175247.GA10263@FreeBSD.cs.nctu.edu.tw> --w33HnxQv0JV2SiT38dt8ljc1pbpdVlKBD Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 8/29/2016 10:52 AM, Li-Wen Hsu wrote: > I guess the quickest way is boot that VM, cd to > /usr/tests/lib/atf/libatf-c++ and run `kyua test atf_c++_test` > However I am not sure this provides enough information because stuff > under /usr/tests/lib/atf/libatf-c++ are all binary files. >=20 > FWIW, I would like to know, should these -target, --sysroot and -B flag= es be > given when compiling a normal program in a normal time? In this test > case, kyua just wanted to compile test.cpp which includes sstream, it's= > not during buildworld/buildkernel time, so files under /usr/obj > should not be used. The flags are only passed in buildworld which uses a sysroot. A direct cd dir && make, will not use them. >=20 > On Mon, Aug 29, 2016 at 10:31:26 -0700, Bryan Drewery wrote: >> This thread is hard to follow. The changes I made shouldn't break >> anything since it's just now acting like an external compiler. >> >> Where is the error so I can debug it? >> >> On 8/29/2016 9:50 AM, Dimitry Andric wrote: >>> Yes, I've also seen the --sysroot options being added recently. I'm = reasonably sure that this is the cause of the error. Bryan did most of t= he restructuring for external toolchains, which also adds the --sysroot o= ption. >>> >>> Is there an usr/include/c++/v1 under the --sysroot? >>> >>> -Dimitry >>> >>>> On 29 Aug 2016, at 18:39, Li-Wen Hsu <lwhsu@FreeBSD.org> wrote: >>>> >>>> Dimitry, are you talking about case lib.atf.libatf-c++.atf_c++_test.= include ? >>>> >>>> I happen to have a r304986 VM here: >>>> >>>> https://people.freebsd.org/~lwhsu/tmp/disk-test.img.xz >>>> >>>> (it starts kyua test in /etc/rc.local, just use ctrl-c to interrupt = it) >>>> >>>> And there is a /usr/include/c++/v1 directory with sstream in it. >>>> >>>> >>>> BTW, I am not sure removing -I/usr/include is the right solution, I= >>>> think this case is checking for "normal" compiling would work, not >>>> during buildworld. When this case was passing, it uses following >>>> command: >>>> >>>> c++ -O2 -pipe -DHAVE_CONFIG_H -I/usr/include -Wall -Werror -o test.o= -c test.cpp >>>> >>>> and now it uses: >>>> >>>> c++ -target x86_64-unknown-freebsd12.0 --sysroot=3D/usr/obj/usr/src/= tmp -B/usr/obj/usr/src/tmp/usr/bin -O2 -pipe -DHAVE_CONFIG_H -I/usr/inclu= de -Wall -Werror -o test.o -c test.cpp >>>> >>>> This changed between r304555 and r304698. >>>> >>>> >>>> Also, does anyone know where is "-I/usr/include" coming from? Is th= is >>>> one? >>>> https://svnweb.freebsd.org/base/head/contrib/atf/atf-c%2B%2B/detail/= test_helpers.cpp?view=3Dmarkup#l56 >>>> >>>> >>>> Li-Wen >>>> >>>> On Mon, Aug 29, 2016 at 16:02:42 +0200, Dimitry Andric wrote: >>>>> Do you have an /usr/include/c++/v1 directory? And is there a file = called "sstream" in it? >>>>> >>>>> If it is there, I think the problem is due to the -I/usr/include op= tion in the command line for the test program. If you remove that, I thi= nk the compilation will work correctly. >>>>> >>>>> -Dimitry >>>>> >>>>>> On 29 Aug 2016, at 14:55, Craig Rodrigues <rodrigc@freebsd.org> wr= ote: >>>>>> >>>>>> Dimitry, >>>>>> >>>>>> During the Jenkins job, I use installworld/installkernel to build = a fully bootable bhyve virtual machine. >>>>>> After the virtual machine boots, ssh into it, and do: >>>>>> >>>>>> cd /usr/tests >>>>>> kyua test >>>>>> kyua report --verbose >>>>>> >>>>>> >>>>>> So I am suspecting that maybe something didn't get installed prope= rly? >>>>>> -- >>>>>> Craig >>>>>> >>>>>> >>>>>> On Mon, Aug 29, 2016 at 4:13 AM, Dimitry Andric <dim@freebsd.org> = wrote: >>>>>> I just found the separate "test results" link in Jenkins. As far = as I can see, one of those failing tests is run as: >>>>>> >>>>>> c++ -target x86_64-unknown-freebsd12.0 --sysroot=3D/builds/workspa= ce/FreeBSD_HEAD/obj/builds/workspace/FreeBSD_HEAD/src/tmp -B/builds/works= pace/FreeBSD_HEAD/obj/builds/workspace/FreeBSD_HEAD/src/tmp/usr/bin -O2 -= pipe -DHAVE_CONFIG_H -I/usr/include -Wall -Werror -o test.o -c test.cpp >>>>>> >>>>>> So are the libc++ headers installed in the /builds/workspace/FreeB= SD_HEAD/obj/builds/workspace/FreeBSD_HEAD/src/tmp sysroot? The compiler = error message appears to indicate it is getting its headers from /usr/inc= lude instead. >>>>>> >>>>>> I can't look on the actual test system, but my guess would be that= either the --sysroot flag is incorrect, or the libc++ headers are not co= rrectly installed on the target system. >>>>>> >>>>>> -Dimitry >>>>>> >>>>>>> On 29 Aug 2016, at 12:56, Dimitry Andric <dim@FreeBSD.org> wrote:= >>>>>>> >>>>>>> Hi Craig, >>>>>>> >>>>>>> I find it very hard to parse these extremely verbose logs. Can y= ou point out the location and contents of the exact error you are seeing?= >>>>>>> >>>>>>> -Dimitry >>>>>>> >>>>>>>> On 29 Aug 2016, at 08:59, Craig Rodrigues <rodrigc@FreeBSD.org> = wrote: >>>>>>>> >>>>>>>> Dimitry, >>>>>>>> >>>>>>>> Can you take a look at this? >>>>>>>> I'm not sure why, but after recent changes, one of the tests is >>>>>>>> complaining that the C++ header <sstream> is missing. >>>>>>>> >>>>>>>> -- >>>>>>>> Craig >>>>>>>> >>>>>>>> >>>>>>>> On Sun, Aug 28, 2016 at 11:11 PM, <jenkins-admin@freebsd.org> wr= ote: >>>>>>>> See <https://jenkins.FreeBSD.org/job/FreeBSD_HEAD/564/>; >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Li-Wen Hsu <lwhsu@FreeBSD.org> >>>> https://lwhsu.org >>> >> >> >> --=20 >> Regards, >> Bryan Drewery >> >=20 >=20 >=20 >=20 --=20 Regards, Bryan Drewery --w33HnxQv0JV2SiT38dt8ljc1pbpdVlKBD-- --8OcGBqASbmaScm8JfvKkt0X3kkQmCjLx6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJXxHa8AAoJEDXXcbtuRpfPnL8IAICmASxkRZREgedHDkot/CTh fB2lIHn2El5cZWYbA49HNAt/h155t9CJbMNfZoqum/m5GGdVV7K8IEOZ5x9qP3LP tsHITaCuW0Gj59pc3sTuumiakSRTrD0DKw2rQTAWlyUzpnc71mzHIzzoxqRtRAlX k3iyZm2i3Wn59JGzVPVvvAHxwtzWmFQdFsFkl7AyDhZvrmehAY7tBnwEL/w80jUY lGrV+gUDuSJPx8dMOmWia4luVROOcT1LgHsWxLHMg5/LRDBjebinQb2nqJv7ifBz o8Y+SRCNsvQeHMpoO5B8GR7wcdYU7hHiHNnX1gjlVNARGKDA2snOqr3z5ymt1ik= =4U6n -----END PGP SIGNATURE----- --8OcGBqASbmaScm8JfvKkt0X3kkQmCjLx6--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?153107ba-094b-3eec-165b-a10080d6d26b>