llvm dev - Aug 2014 - [LLVMdev] Plans for the Apple supported Darwin buildbot cluster

On 14 August 2014 10:41, David Chisnall <David.Chisnall at cl.cam.ac.uk>
wrote:
> I've put the diff in Phabricator here:
>
> http://reviews.llvm.org/D4901
>
> If you think it looks vaguely sensible then let me know and I'll commit
it.
Hi David,

Is there an option for "make check-all"? Or do you have to call lit in
a special way inside Jenkins?

--renato

On 14 Aug 2014, at 11:05, Renato Golin <renato.golin at linaro.org> wrote:
> Is there an option for "make check-all"? Or do you have to call
lit in
> a special way inside Jenkins?
Our Jenkins config just runs llvm-lit manually after building (we use Ninja not
make in Jenkins because it's vastly faster for incremental builds and we
have several LLVM forks / versions that we test).  I agree that having a make /
ninja target for the check would be useful, but the lit option was the minimum
work we needed to get the pretty graphs out of Jenkins (and, more importantly,
the regression emails).

Note that Jenkins doesn't have a default location for the XML file either,
so we end up specifying this in the llvm-lit command and in the Jenkins config. 
It might be nice for the check-all-xml (or whatever) target to put it in a fixed
location so people configuring Jenkins just need to tell it where to look in one
place.

David

On 14 August 2014 11:13, David Chisnall <David.Chisnall at cl.cam.ac.uk>
wrote:
> Our Jenkins config just runs llvm-lit manually after building (we use Ninja
not make in Jenkins because it's vastly faster for incremental builds and we
have several LLVM forks / versions that we test).  I agree that having a make /
ninja target for the check would be useful, but the lit option was the minimum
work we needed to get the pretty graphs out of Jenkins (and, more importantly,
the regression emails).
I use ninja, too. And ccache. And shared libs for debug builds. And gold. :)

> Note that Jenkins doesn't have a default location for the XML file
either, so we end up specifying this in the llvm-lit command and in the Jenkins
config.  It might be nice for the check-all-xml (or whatever) target to put it
in a fixed location so people configuring Jenkins just need to tell it where to
look in one place.
Can't it be the output of a verbose build, like the textual version?

--renato