search for: smooshlab

...>> FYI, if you want to check the encoding of an instruction, you can do so >> with a command like this: > > Thanks. It's strange that the buidbot shows this test failing long before I > made the change. Why would that be? It didn't. Here's a good build: http://smooshlab.apple.com:8010/builders/clang-i386-darwin9/builds/5019 The following two builds are broken by your previous bug: http://smooshlab.apple.com:8010/builders/clang-i386-darwin9/builds/5020 http://smooshlab.apple.com:8010/builders/clang-i386-darwin9/builds/5021 with that fixed, the subsequent builds f...

...le not under version control for local testing. Either we need to make it so that the buildbot master (/buildbot/osuosl/master) can operate in two modes (normal and localhost testing) or we need to provide another buildbot master configuration for localhost testing. I think this is what ``buildbot/smooshlab`` is for but that code has not been touched in ages and is probably dead (if it is dead, we should delete it). Other issues ========== * Ancient version of buildbot. Why do we use buildbot 0.8.5? Newer versions are available in Pypi which anyone using Python can install. I have issues with 0.8....

...s far as I know, we work with any recent version of slaves. Bounding the "dev/test setup" to any specific version could be easily avoided by choosing a right builder. So, this should not be a problem for someone who would wont to develop and test a build factory. > * llvmlab, osuosl, smooshlab? Reorganizing this currently is a work in progress. osuosl is in use; llvmlab is in use but will be decommissioned; smooshlab is used internally and is pending to be removed. In general, if you don't feel comfortable developing and debugging a build factory for the buildbot, you can always us...

...lot of different URL's in IRC, but no list so I can > check "all of the waterfalls". I'm not talking about the specific bots > (e.g. llvm-x86_64-ubuntu) but the "fleets" (e.g.http://lab.llvm.org). Publicly there's just the one fleet. On IRC you'll also see smooshlab, Apple's internal buildmaster/fleet, reporting (but you can't access its web view, etc - all you get is the IRC failure notices (& maybe email failure notices)). I don't think anyone else has publicly reporting LLVM buildmasters. > Could you maybe add a little bulleted list (or...

...RL's in IRC, but no list so I can >> check "all of the waterfalls". I'm not talking about the specific bots >> (e.g. llvm-x86_64-ubuntu) but the "fleets" (e.g.http://lab.llvm.org). > > Publicly there's just the one fleet. On IRC you'll also see smooshlab, > Apple's internal buildmaster/fleet, reporting (but you can't access > its web view, etc - all you get is the IRC failure notices (& maybe > email failure notices)). > > I don't think anyone else has publicly reporting LLVM buildmasters. Here's a (non exhausti...

On Monday 15 February 2010 15:08:22 Chris Lattner wrote: > On Feb 15, 2010, at 1:04 PM, David Greene wrote: > >> FWIW, this is because you broke the encoding of an instruction in your > >> patch. This is incorrect: > >> > >> +def MOVNTDQ_64mr : PSI<0xE7, MRMDestMem, (outs), (ins f128mem:$dst, > >> VR128:$src), +

Cool! This is great news. I feel like this information should be in our documentation somewhere. Could you start a new file ContinuousIntegration.rst and use this content to seed it? This new page would also be a good place to mention some LLVM idiosyncrasies like smooshlab being Apple-internal but still reporting via IRC; these things have not had a good place to be put yet. AFAIK currently our continuous integration infrastructure is mostly community wisdom and besides a small mention of some of the reporting bots on index.rst there is no documentation describing it...

On Feb 15, 2010, at 1:04 PM, David Greene wrote: >> FWIW, this is because you broke the encoding of an instruction in your >> patch. This is incorrect: >> >> +def MOVNTDQ_64mr : PSI<0xE7, MRMDestMem, (outs), (ins f128mem:$dst, >> VR128:$src), + "movntdq\t{$src, $dst|$dst, $src}", >> + [(alignednontemporalstore

..., but no list so I can >>> check "all of the waterfalls". I'm not talking about the specific bots >>> (e.g. llvm-x86_64-ubuntu) but the "fleets" (e.g.http://lab.llvm.org). >> >> Publicly there's just the one fleet. On IRC you'll also see smooshlab, >> Apple's internal buildmaster/fleet, reporting (but you can't access >> its web view, etc - all you get is the IRC failure notices (& maybe >> email failure notices)). >> >> I don't think anyone else has publicly reporting LLVM buildmasters. > &gt...

...ngw32 To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> The buildbot build-self-4-mingw32 is failing with an assertion: Assertion failed: (isStackEmpty() && "Stack not empty at end of basic block?"), function processBasicBlock, file /Users/buildslave/zorg/buildbot/smooshlab/slave/build-self-4-mingw32/llvm.src/lib/Target/X86/X86FloatingPoint.cpp, line 305. Could anyone produce a bitcode file for that failure, please?---------- Forwarded message ---------- From: Jakob Stoklund Olesen <stoklund at 2pi.dk> Date: Sun, Jul 11, 2010 at 03:22 Subject: [LLVMdev] Bitcode...

...I can >>>> check "all of the waterfalls". I'm not talking about the specific bots >>>> (e.g. llvm-x86_64-ubuntu) but the "fleets" (e.g.http://lab.llvm.org). >>> >>> Publicly there's just the one fleet. On IRC you'll also see smooshlab, >>> Apple's internal buildmaster/fleet, reporting (but you can't access >>> its web view, etc - all you get is the IRC failure notices (& maybe >>> email failure notices)). >>> >>> I don't think anyone else has publicly reporting LLVM bu...

...ck the encoding of an instruction, you can do so > >> with a command like this: > > > > Thanks. It's strange that the buidbot shows this test failing long > > before I made the change. Why would that be? > > It didn't. Here's a good build: > http://smooshlab.apple.com:8010/builders/clang-i386-darwin9/builds/5019 Well, I can't get there, but... Oh. Buildbot is not displaying what I would expect. Looking at the Console (revision-oriented) Display, I was looking for errors listed under the color- keyed build results. For example: clang-i386-aur...

Hello LLVM Dev and Clang Dev! David Dean and I just finished bringing up a new build master on lab.llvm.org, llvmlab, which is located at the url http://lab.llvm.org:8013 and is in #llvm under the username llvmlab. llvmlab is different than the current buildbot based continuous integration systems llvm uses; llvmlab is a phased builder based system. The high level details of the phased builder

...ow when there is a problem. Our machine might not be able to keep up with a build for every commit but could do regular timed builds. The blame list won't be as precise but at least we'll all know if something goes wrong. Would we create a directory in zorg along the lines of the osuosl, smooshlab, etc. directories under zorg/buildbot? Hopefully we can just integreate into osuosl but we might not be able to due to security considerations, among other things. -David

The buildbot build-self-4-mingw32 is failing with an assertion: Assertion failed: (isStackEmpty() && "Stack not empty at end of basic block?"), function processBasicBlock, file /Users/buildslave/zorg/buildbot/smooshlab/slave/build-self-4-mingw32/llvm.src/lib/Target/X86/X86FloatingPoint.cpp, line 305. Could anyone produce a bitcode file for that failure, please? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 1929 bytes Desc:...

I'd like to take code ownership of the LLVM Buildbot code. Thanks Galina

kinda random, but do we have a centralized list of all of the buildbots? I see a lot of different URL's in IRC, but no list so I can check "all of the waterfalls". I'm not talking about the specific bots (e.g. llvm-x86_64-ubuntu) but the "fleets" (e.g.http://lab.llvm.org). Could you maybe add a little bulleted list (or link to a list) to docs/HowToAddABuilder.rst?

...not have this problem. Please let me know if you have questions, problems, or suggestions. For those interested in how it is setup, most of the configuration stuff is now checked in to the LLVM repository at http://llvm.org/svn/llvm-project/zorg The particular version of buildbot we run is the smooshlab branch in my public fork: http://github.com/ddunbar/buildbot/ Cheers, - Daniel

...are setup) is that they try to build on every commit, if commits come in while a build is running, those will be rolled up into a build starting immediately after the current one finishes. Obviously the fewer commits per > Would we create a directory in zorg along the lines of the osuosl, > smooshlab, etc. directories under zorg/buildbot? I just checkout the zorg repository & run my local buildmaster out of that. I don't contribute this code upstream - there doesn't seem to be much point in doing so. > Hopefully we can just integreate into osuosl but we might not be able to &gt...