things are green, nice catch on the job config, josh. On Mon, Oct 19, 2015 at 1:57 PM, shane knapp <skn...@berkeley.edu> wrote: > ++joshrosen > > some of those 1.4 builds were incorrectly configured and launching on > a reserved executor... josh fixed them and we're looking a lot better > (meaning that we're building and not failing at launch). > > shane > > On Mon, Oct 19, 2015 at 1:49 PM, Patrick Wendell <pwend...@gmail.com> wrote: >> I think many of them are coming form the Spark 1.4 builds: >> >> https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Test%20(Dashboard)/job/Spark-1.4-Maven-pre-YARN/3900/console >> >> On Mon, Oct 19, 2015 at 1:44 PM, Patrick Wendell <pwend...@gmail.com> wrote: >>> >>> This is what I'm looking at: >>> >>> >>> https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Test%20(Dashboard)/ >>> >>> >>> >>> On Mon, Oct 19, 2015 at 12:58 PM, shane knapp <skn...@berkeley.edu> wrote: >>>> >>>> all we did was reboot -05 and -03... i'm seeing a bunch of green >>>> builds. could you provide me w/some specific failures so i can look >>>> in to them more closely? >>>> >>>> On Mon, Oct 19, 2015 at 12:27 PM, Patrick Wendell <pwend...@gmail.com> >>>> wrote: >>>> > Hey Shane, >>>> > >>>> > It also appears that every Spark build is failing right now. Could it >>>> > be >>>> > related to your changes? >>>> > >>>> > - Patrick >>>> > >>>> > On Mon, Oct 19, 2015 at 11:13 AM, shane knapp <skn...@berkeley.edu> >>>> > wrote: >>>> >> >>>> >> worker 05 is back up now... looks like the machine OOMed and needed >>>> >> to be kicked. >>>> >> >>>> >> On Mon, Oct 19, 2015 at 9:39 AM, shane knapp <skn...@berkeley.edu> >>>> >> wrote: >>>> >> > i'll have to head down to the colo and see what's up with it... it >>>> >> > seems to be wedged (pings ok, can't ssh in) and i'll update the list >>>> >> > when i figure out what's wrong. >>>> >> > >>>> >> > i don't think it caught fire (#toosoon?), because everything else is >>>> >> > up and running. :) >>>> >> > >>>> >> > shane >>>> >> >>>> >> -- >>>> >> You received this message because you are subscribed to the Google >>>> >> Groups >>>> >> "amp-infra" group. >>>> >> To unsubscribe from this group and stop receiving emails from it, send >>>> >> an >>>> >> email to amp-infra+unsubscr...@googlegroups.com. >>>> >> For more options, visit https://groups.google.com/d/optout. >>>> > >>>> > >>>> > -- >>>> > You received this message because you are subscribed to the Google >>>> > Groups >>>> > "amp-infra" group. >>>> > To unsubscribe from this group and stop receiving emails from it, send >>>> > an >>>> > email to amp-infra+unsubscr...@googlegroups.com. >>>> > For more options, visit https://groups.google.com/d/optout. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "amp-infra" group. >>>> To unsubscribe from this group and stop receiving emails from it, send an >>>> email to amp-infra+unsubscr...@googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >>> >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "amp-infra" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to amp-infra+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout.
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
