> I've been working to revive the PPC64 build bots, and succeeded, but
> not for the right reasons. There were still bootstrap assertion
> failures and other pretty blatant errors. Then we figured out why:
> the Clang bootstrapping build bots for Power7 are not actually
> running any of the Clang tests!
> Could one of you tweak this build bot's configuration to match the
> other bootstrap bot configurations that run both LLVM and Clang tests?
So ignoring the ppc64-elf-linux2 bot (which is redundant wrt the
ppc64-elf-linux1 bot), Powerpc64 has three unique buildbots going; the
relevant 'factory' entries for them are so:
I'm happy to change those or add another if desired, but will need
additional input on 'what'.
Maybe I'm confused somehow, but I thought this one:
does bootstrap and then run both LLVM and Clang tests (successfully):
Correct, or at least that is the intent.
The other Clang PPC64 build bot tries to run lnt.nightly-test:
but fails (and has always been failing); one problem seems to
be that altivec is disabled for some reason? It's been on my
to-do list to check what's going on here ...
Correct. This was the first clang buildbot that I set up, and it is
configured to do the LNT tests.
> Is there a a Clang PPC64 build bot that *doesn't* self-host so we
> can get faster turn around?
> I think the ideal configuration is:
> 1) normal clang-test-only build bot
> 2) normal llvm-test-only build bot
> 3) bootstrap a new toolchain, and then run clang+llvm tests.
Besides the two bots mentioned above, there's also two LLVM bots:
which simply build and test LLVM only. (Not sure why there's
two of them, they seem to be doing the same thing. Will?)
They are on different host systems, but are redundant with respect to
each other as far as the llvm testing goes. If having two complicates
things, I can disable the second.