Date: Thu, 10 Jun 2010 00:20:21 +0200 From: Pawel Worach <pawel.worach@gmail.com> To: Garrett Cooper <yanefbsd@gmail.com> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r208954 - in head/contrib/llvm: . docs test tools/clang tools/clang/docs tools/clang/test website Message-ID: <82F59C7F-7984-449A-BA04-796F0A17DC3E@gmail.com> In-Reply-To: <AANLkTinlzRhxSk84MfFXHWwTdnV6MC_tqw1uimkwU99_@mail.gmail.com> References: <201006091759.o59HxrJw096803@svn.freebsd.org> <AANLkTinHk6hZrCxBuyCiIiFSkCuAnN2ZnlmIsrhChQp-@mail.gmail.com> <20100609190445.GE56080@hoeg.nl> <AANLkTinlzRhxSk84MfFXHWwTdnV6MC_tqw1uimkwU99_@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 9, 2010, at 23:58, Garrett Cooper wrote: > On Wed, Jun 9, 2010 at 12:04 PM, Ed Schouten <ed@80386.nl> wrote: >> Hi Garrett, >>=20 >> * Garrett Cooper <yanefbsd@gmail.com> wrote: >>> Why strip test? This might actually be helpful for folks trying to >>> evaluate whether or not they should upgrade to newer versions of >>> clang. >>=20 >> The testsuite can be checked out separately from the vendor space. It >> will account for about 50 MB of additional disk space usage. >=20 > Yes, but the tests can change at any point in time and might not > reflect the code stored in the repository. >=20 > Could a note at least be provided, or a port maintained to help others > (say vendors) who have to qualify FreeBSD that this is the particular > version that needs to be picked up from <blah> in order to test our > shiny new compiler? That would make things considerably easier to work > with, as I've worked as QA in a Linux shop in the past, where a lot of > Linux provided packages that we had in the tree did not have the > associated test code, and as QA that made my job a pain to deal with. >=20 > Just a small file that stated where and/or how to obtain things would > make this a lot easier. >=20 > I would think that developers would also like the same to see whether > or not there are any particular known issues with clang/llvm. >=20 We have a buildbot running here[1] that has the goal of serving as a = qualification system. It does a nightly build of llvm/clang trunk in a self-host config, runs = the test suite in both stages and then builds freebsd trunk world+kernel = and boots the result. [1] http://amd64-clang-bot.qat.freebsd.org:8010/waterfall --=20 Pawel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?82F59C7F-7984-449A-BA04-796F0A17DC3E>