++joshrosen On Mon, Oct 9, 2017 at 1:48 AM, Sean Owen <so...@cloudera.com> wrote:
> I'm seeing jobs killed regularly, presumably because the time out (210 > minutes?) > > https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA% > 20Test%20(Dashboard)/job/spark-master-test-maven-hadoop-2.6/3907/console > > Possibly related: this master-SBT-2.7 build hasn't passed in weeks: > > https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA% > 20Test%20(Dashboard)/job/spark-master-test-sbt-hadoop-2.7/ > > All seem to be timeouts, explicilty or implicitly. > > I know the answer is make tests faster, but failing that, can we raise the > timeout again to ... 4 hours ? or maybe I misread why these are being > killed? > > If somehow it's load on Jenkins servers, we could consider getting rid of > the two different Hadoop builds as I think it serves little purpose to > build separately for the two (or even support 2.6 specially). >
