Here is a trivial reason why I have not propagated http://bb.pgr.jp/ . Sometimes (but I suppose rarely) he reports false alarm in a few points. He'd send blames to the llvm-testresults if his master (aka I) knew he were mature. I don't also want him promoted and called as one of official buildbots. He is my pet, though, I expect he should be helpful to the developers. ...Takumi 2012/11/16 Benjamin Kramer <benny.kra at gmail.com>:> > On 15.11.2012, at 23:16, David Blaikie <dblaikie at gmail.com> wrote: > >> On Thu, Nov 15, 2012 at 2:10 PM, Sean Silva <silvas at purdue.edu> wrote: >>> 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). >> >> 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 exhaustive) list: > > - http://lab.llvm.org:8011/ the main fleet, and the only one that sends mails > - http://smooshlab.apple.com:8013/ apple's set of internal builders, not reachable from outside the mothership > - http://bb.pgr.jp/ chapuni's bots, including some fast incremental builders and windows bots > - http://llvm-amd64.freebsd.your.org:8010/ freebsd builders, continuously build the fbsd kernel among other things > - http://buildbot.llvm.linuxfoundation.org/ builds the linux kernel with clang > > There are probably even more buildbots around, private and public. A list in the documentation will probably become outdated quickly as some of those bots come and go. > > - Ben > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
> Here is a trivial reason why I have not propagated http://bb.pgr.jp/ . > Sometimes (but I suppose rarely) he reports false alarm in a few > points. He'd send blames to the llvm-testresults if his master (aka I) > knew he were mature. > > I don't also want him promoted and called as one of official > buildbots. He is my pet, though, I expect he should be helpful to the > developers.Is <http://bb.pgr.jp/builders/cmake-clang-i686-msvc10> our only MSVC builder? lab.llvm.org doesn't seem to have one. I think that it's valuable to have an MSVC builder around so we *nix folks don't inadvertently break things there. -- Sean Silva On Thu, Nov 15, 2012 at 10:04 PM, NAKAMURA Takumi <geek4civic at gmail.com> wrote:> Here is a trivial reason why I have not propagated http://bb.pgr.jp/ . > Sometimes (but I suppose rarely) he reports false alarm in a few > points. He'd send blames to the llvm-testresults if his master (aka I) > knew he were mature. > > I don't also want him promoted and called as one of official > buildbots. He is my pet, though, I expect he should be helpful to the > developers. > > ...Takumi > > > 2012/11/16 Benjamin Kramer <benny.kra at gmail.com>: >> >> On 15.11.2012, at 23:16, David Blaikie <dblaikie at gmail.com> wrote: >> >>> On Thu, Nov 15, 2012 at 2:10 PM, Sean Silva <silvas at purdue.edu> wrote: >>>> 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). >>> >>> 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 exhaustive) list: >> >> - http://lab.llvm.org:8011/ the main fleet, and the only one that sends mails >> - http://smooshlab.apple.com:8013/ apple's set of internal builders, not reachable from outside the mothership >> - http://bb.pgr.jp/ chapuni's bots, including some fast incremental builders and windows bots >> - http://llvm-amd64.freebsd.your.org:8010/ freebsd builders, continuously build the fbsd kernel among other things >> - http://buildbot.llvm.linuxfoundation.org/ builds the linux kernel with clang >> >> There are probably even more buildbots around, private and public. A list in the documentation will probably become outdated quickly as some of those bots come and go. >> >> - Ben >> >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
2012/11/16 Sean Silva <silvas at purdue.edu>:>> Here is a trivial reason why I have not propagated http://bb.pgr.jp/ . >> Sometimes (but I suppose rarely) he reports false alarm in a few >> points. He'd send blames to the llvm-testresults if his master (aka I) >> knew he were mature. >> >> I don't also want him promoted and called as one of official >> buildbots. He is my pet, though, I expect he should be helpful to the >> developers. > > Is <http://bb.pgr.jp/builders/cmake-clang-i686-msvc10> our only MSVC > builder? lab.llvm.org doesn't seem to have one. I think that it's > valuable to have an MSVC builder around so we *nix folks don't > inadvertently break things there.AFAIK the only one in public. I know Apple has the builder, though it is invisible to us. In a few years ago, 2009 builder was in the public buildbot, (IIRC, maintained by ddunbar). It gone. Now the builder is using Japanese version of MSC16. I am planning to introduce English version of MSC17 in future. I am also planning to provide some configurations on it, for example, Debug builds and x64 builds. Tips: Please ask error codes Cxxxx to msdn or google, if error messages would be hard for you to read.