Jenkins build is still unstable: FreeBSD_HEAD #564

[Li-Wen Hsu]

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=/usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/bin -O2 -pipe -DHAVE_CONFIG_H -I/usr/include -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 this
one?
https://svnweb.freebsd.org/base/head/contrib/atf/atf-c%2B%2B/detail/test_helpers.cpp?view=markup#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 option in the command line for the test program.  If you remove that, I think the compilation will work correctly.
> 
> -Dimitry
> 
> > On 29 Aug 2016, at 14:55, Craig Rodrigues <rodrigc at freebsd.org> wrote:
> > 
> > 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 properly?
> > --
> > Craig
> > 
> > 
> > On Mon, Aug 29, 2016 at 4:13 AM, Dimitry Andric <dim at 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=/builds/workspace/FreeBSD_HEAD/obj/builds/workspace/FreeBSD_HEAD/src/tmp -B/builds/workspace/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/FreeBSD_HEAD/obj/builds/workspace/FreeBSD_HEAD/src/tmp sysroot?  The compiler error message appears to indicate it is getting its headers from /usr/include 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 correctly installed on the target system.
> > 
> > -Dimitry
> > 
> > > On 29 Aug 2016, at 12:56, Dimitry Andric <dim at FreeBSD.org> wrote:
> > >
> > > Hi Craig,
> > >
> > > I find it very hard to parse these extremely verbose logs.  Can you point out the location and contents of the exact error you are seeing?
> > >
> > > -Dimitry
> > >
> > >> On 29 Aug 2016, at 08:59, Craig Rodrigues <rodrigc at 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 at freebsd.org> wrote:
> > >> See <https://jenkins.FreeBSD.org/job/FreeBSD_HEAD/564/>
> > >>
> > >>
> > >
> > 
> > 
> 



-- 
Li-Wen Hsu <lwhsu at FreeBSD.org>
https://lwhsu.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 931 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-testing/attachments/20160830/9c5d26f8/attachment.sig>