Date: Tue, 30 Aug 2016 01:45:41 -0700 From: "Ngie Cooper (yaneurabeya)" <yaneurabeya@gmail.com> To: Bryan Drewery <bdrewery@FreeBSD.org> Cc: Li-Wen Hsu <lwhsu@FreeBSD.org>, "jenkins-admin@freebsd.org" <jenkins-admin@freebsd.org>, "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org>, Dimitry Andric <dim@FreeBSD.org> Subject: Re: Jenkins build is still unstable: FreeBSD_HEAD #564 Message-ID: <BA574AB2-1B02-4F04-BBA2-A3BCB90F3DB3@gmail.com> In-Reply-To: <5485945b-6539-5ed0-c089-5537d6bd70a9@FreeBSD.org> 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> <CAA41D00-2451-42EC-B9FD-3E31F42F9CF6@gmail.com> <31f11ba3-ca29-0f85-f1c1-6a3cd467bb57@FreeBSD.org> <67E84707-3267-49F3-8DB6-13CBD05B1690@gmail.com> <B014DD06-4BB2-4503-8908-C78EFEE0FCA2@gmail.com> <3B60A57F-778C-4E7C-B081-098C0F6E92D2@gmail.com> <F144F428-A8B6-4E95-999E-D20B0A7B62C2@gmail.com> <5485945b-6539-5ed0-c089-5537d6bd70a9@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_241FCF02-82E4-489E-AB04-B22E9BC58334 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Aug 29, 2016, at 11:20, Bryan Drewery <bdrewery@FreeBSD.org> wrote: =E2=80=A6 > Trust me, you're wasting your time, this is not the problem. If it = were > then _nothing_ would compile from the /usr/bin/cc compiler. It's only = a > problem with running the ATF tests which means it is likely storing = the > flags it is built with somewhere and reusing them. Well, that was part of the problem, but it seems that clang is indeed = caching -sysroot when running the _everything phase of buildworld. =46rom = https://jenkins.freebsd.org/job/FreeBSD_HEAD/571/consoleText : 50585 --- AnalysisDeclContext.o --- 50586 c++ -O2 -pipe = -I/builds/workspace/FreeBSD_HEAD/src/lib/clang/libclanganalysis/../../../c= ontrib/llvm/include = -I/builds/workspace/FreeBSD_HEAD/src/lib/clang/libclanganalysis/../../../c= ontrib/llvm/ tools/clang/include = -I/builds/workspace/FreeBSD_HEAD/src/lib/clang/libclanganalysis/../../../c= ontrib/llvm/tools/clang/lib/Analysis -I. = -I/builds/workspace/FreeBSD_HEAD/src/lib/clang/libclanganaly = sis/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX = -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS = -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=3D\"x86_64-unknow = n-freebsd12.0\" -DLLVM_HOST_TRIPLE=3D\"x86_64-unknown-freebsd12.0\" = -DDEFAULT_SYSROOT=3D\"/builds/workspace/FreeBSD_HEAD/obj/builds/workspace/= FreeBSD_HEAD/src/tmp\" -MD -MF.depend.AnalysisDeclContext .o = -MTAnalysisDeclContext.o -Qunused-arguments = -I/builds/workspace/FreeBSD_HEAD/obj/builds/workspace/FreeBSD_HEAD/src/tmp= /legacy/usr/include -std=3Dc++11 -fno-exceptions -fno-rtti = -stdlib=3Dlibc++ - Wno-c++11-extensions -c = /builds/workspace/FreeBSD_HEAD/src/lib/clang/libclanganalysis/../../../con= trib/llvm/tools/clang/lib/Analysis/AnalysisDeclContext.cpp -o = AnalysisDeclContext.o The reason why =E2=80=9Cno one=E2=80=9D has seen this probably is this = is that is: - not default (using an inaccessible ${WORLDTMP} from an install image; = path isn=E2=80=99t standard). - ^/stable/11 is still a fairly fresh branch and the number of people = testing on ^/head is likely smaller than the ^/stable/... branches. Thanks, -Ngie --Apple-Mail=_241FCF02-82E4-489E-AB04-B22E9BC58334 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJXxUe1AAoJEPWDqSZpMIYVdD0P/0ijDngZ4MZPK2mSdfb/202A tfCVkJVTryw+CGf/ilIpI6YTVCdsTkCgmBhkZORlyC0sxzy1oBRFQfzBJ23uVQ7C oJq/fMe6k8gI2RaruOW33+U3/IlM0Twa9kxXiWT+Z6npow7PHryOBl+TRa3UeQSq HUfvZrrLiF57oAakTopjrmicoZKXyRqyNDlY2Q3MPXeJPA+iYMlMb4IiF2q10Fw4 rVusOaTc5GackpwGuDuPwwgNQEIZ4GwAIpf1G6RLkD2Olpji9pLN/UY4e2Rnk5Eg LauHWFRfdvd9yd5lEkLuZRYvVkdL7KPAvQn2TZHaBQM/ktPPO7mzgsLY58DLCXm6 QwUziyJzwo+lIKOevJH7uSURczlKv7Z9FELqrq6NAqXqCisCRsIBSd6GCBja/aou FmtUYsUpNm115kYVlCUSRE4fuzid1/3BO4UMm/sm3NHCx6Q702LW6ZlVuz8dUcCl qZMX5zD8MEH0KDDmdhRcnZTJ4nWn5XM+AukkqY5DpSz4hDFgJBB5R0WD0GT/kqLg ApadF/76ZZb3r5PMSGBj49pxlE3dV2rWkxETcICtc4SM5OgI56df9ICpQDuSxreZ H9xvQ7RfmUE3IZ5rELBsHr+cp9qt5GYAKrhvt+uA5CatrmirEdxo/nJQsRWNjLNk tdQM9Iqqz05RRfubYVkF =S1D1 -----END PGP SIGNATURE----- --Apple-Mail=_241FCF02-82E4-489E-AB04-B22E9BC58334--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BA574AB2-1B02-4F04-BBA2-A3BCB90F3DB3>