search for: getllvmbuildfactory

...======================================================= --- buildbot/osuosl/master/config/builders.py (revision 203958) +++ buildbot/osuosl/master/config/builders.py (working copy) @@ -90,6 +90,8 @@ 'builddir':"llvm-mips-linux", 'factory': LLVMBuilder.getLLVMBuildFactory("mips-linux-gnu", timeout=40, config_name='Release+Asserts', extra_configure_args=["--with-extra-options=-mips32r2", + "CC=/mips/proj/build-compiler/clang-be-o32-r203581/bin/clang", + "CXX=/mips/proj/build-compiler/clang-be-o32-r203581/bin/cla...

...s.py (revision 143312) +++ master/config/builders.py (working copy) @@ -48,7 +48,7 @@ {'name': "llvm-ppc-darwin", 'slavenames':["arxan_bellini"], 'builddir':"llvm-ppc-darwin", - 'factory': LLVMBuilder.getLLVMBuildFactory("ppc-darwin", jobs=1, clean=True, + 'factory': LLVMBuilder.getLLVMBuildFactory("ppc-darwin", jobs=2, clean=True, config_name = 'Release', env = { 'CC' : "/usr/bin/gcc-4.2",...

...er multiple failures. To make sure the slave is ready, you can start from manually building and testing everything you want the build to do on that slave in context of the account the build slave will be running in. If you succeed, then the slave is likely ready. You patch doesn't look right. getLLVMBuildFactory does not support cmake, so it wouldn't do what you think it will. For the same reason your slave properties (jobs and loadaverage) wouldn't work. See zorg/buildbot/builders/LLVMBuilder.py for more details. You either build LLVM with configure (this is what the existing LLVM factory does),...

...y, you can start from manually building and >> testing everything you want the build to do on that slave in context of the >> account the build slave will be running in. >> If you succeed, then the slave is likely ready. >> >> You patch doesn't look right. >> getLLVMBuildFactory does not support cmake, so it wouldn't do what you think >> it will. For the same reason your slave properties (jobs and loadaverage) >> wouldn't work. >> See zorg/buildbot/builders/LLVMBuilder.py for more details. >> >> You either build LLVM with configure (th...

...erything you want the build to do on that slave in context of >> >> the >> >> account the build slave will be running in. >> >> If you succeed, then the slave is likely ready. >> >> >> >> You patch doesn't look right. >> >> getLLVMBuildFactory does not support cmake, so it wouldn't do what you >> >> think >> >> it will. For the same reason your slave properties (jobs and >> >> loadaverage) >> >> wouldn't work. >> >> See zorg/buildbot/builders/LLVMBuilder.py for more deta...

Dmitri Gribenko <gribozavr at gmail.com> writes: >> Right, I get that. Actually I would probably use --enable-werror. >> >> Should I create a patch for builders.py to add a new config? > > Yes. Send it to llvm-commits and CC Galina Kistanova. Ok, cool. Thanks! >> Is there a way to map a config so that it only even builds on a certain >> buildslave?

Hi all, I'm working on adding a new buildbot. I'm don't understand what is required when patching zorg's builders.py and slaves.py. Is there any documentation on this? Would anybody be willing to help? Best, Eric Fiselier -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi everyone, I am working with Alexei Starovoitov to contribute an LLVM buildbot for the experimental BPF backend. I am following the steps at [1] to setup a buildbot and I was mostly successful: I was able to setup a slave and a temporary master to check its base config. Now I'm not sure about the next step: patching the "slaves.py" and "builders.py" files in zorg. * Is

Chandler Carruth <chandlerc at gmail.com> wrote: > 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

Hey Galina, Will; 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