On Sat, Jan 22, 2011 at 01:44:53PM +0100, Roman Divacky wrote: > On Sat, Jan 22, 2011 at 02:12:36PM +0200, Kostik Belousov wrote: > > On Sat, Jan 22, 2011 at 01:45:36AM +0000, > > [email protected] wrote: > > > The Buildbot has detected a new failure on builder freebsd-clang-i386 > > > while building llvm. > > > Full details are available at: > > > > > > http://llvm-amd64.freebsd.your.org:8010/builders/freebsd-clang-i386/builds/57 > > > > > > Buildbot URL: http://llvm-amd64.freebsd.your.org:8010/ > > > > > > Buildslave for this Build: freebsd-i386 > > > > > > Build Reason: scheduler > > > Build Source Stamp: 123999 > > > Blamelist: djg,venkatra > > > > > > BUILD FAILED: failed compile-freebsd-world > > > > > > sincerely, > > > -The Buildbot > > Can we remove this bot from freebsd-toolchain@, please ? > > There is nothing that freebsd developers are responsible for, nor can fix. > > I agree that it does not make much sense to report when freebsd world > is broken (with any compiler) nor when llvm is broken everywhere and not only > on freebsd. > > On the other hand I think it's very useful to know when llvm breaks on freebsd > only or when freebsd world is not compilable with llvm (be it a bug in freebsd > that gcc does not catch or llvm bug). My take is that would be indeed useful to have tinderbox-like reports for world and kernel compiled with _in-tree_ llvm. I am fine with receiving llvm-buildworld failures that duplicate the failures from gcc tinderbox.
Anything else should be kept to llvm lists or anybody private mailings. > > I dont know how to achieve this, any ideas? > > Anyway, the number of mails should go down, it's spamming a little too much. > > roman
pgpqws71sZv1w.pgp
Description: PGP signature
