search for: informativemailnotifi

...ental backend. > > I see. I had followed the generic How to add a builder <http://llvm.org/docs/HowToAddABuilder.html> docs, which doesn’t mention the concept of an experimental buildbot. I’ll send a patch to mention it. > > If you want to do the same, then you’ll need to add an InformativeMailNotifier to http://llvm.org/svn/llvm-project/zorg/trunk/buildbot/osuosl/master/config/status.py <http://llvm.org/svn/llvm-project/zorg/trunk/buildbot/osuosl/master/config/status.py>. > > Nice! Exactly what I was looking for. > > If we would believe the AVR backend is stable enough, suc...

> On Feb 3, 2017, at 4:18 AM, Tobias Grosser via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Fri, Feb 3, 2017, at 11:37 AM, Dylan McKay via llvm-dev wrote: >> Hey all, >> >> Every few weeks, a change is committed to trunk that breaks the AVR >> buildbot. >> >> A problem presents when commit authors do not fix the build, and just

Hey all, Every few weeks, a change is committed to trunk that breaks the AVR buildbot. A problem presents when commit authors do not fix the build, and just leave it because it passes on the core buildbots. The build stays red for a few days until I go and check it. In the meantime, it likely causes spam for most if not all developers when they commit new code. All commits should keep master