+1. Colin
On Mon, Nov 30, 2015 at 11:33 AM, Andrew Wang <andrew.w...@cloudera.com> wrote: > Good point Allen. So I guess the broader question is, do we find the > per-commit tracking build and test useful? With our current flakiness > levels, there isn't much signal from a FAILED on one of these integration > jobs. I think Hadoop-trunk-Commit is still nice as a compilation check. > > So overall I'm still in favor of disabling the other jobs. There's always > the backstop of the nightly test runs to help track down new failures, and > doing a one-day bisect shouldn't be too bad. > > If this sounds good, I'll go ahead and do the above. > > Best, > Andrew > > On Thu, Nov 26, 2015 at 9:22 AM, Allen Wittenauer <a...@altiscale.com> wrote: > >> >> > On Nov 25, 2015, at 5:41 PM, Andrew Wang <andrew.w...@cloudera.com> >> wrote: >> > >> > Hi all, >> > >> > Right now we get something like 7 comments from Hudson whenever a change >> is >> > committed. Would anyone object if I turned off 6 of them? We have >> > variations like: >> > >> > Hadoop-trunk-Commit >> > Hadoop-Hdfs-trunk-Java8 >> > Hadoop-Yarn-trunk >> > ...etc >> > >> > I propose leaving notifications on for just Hadoop-trunk-Commit. >> > >> >> This will give false positives since that job does a -DskipTests. >>
