hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Hsieh <...@cloudera.com>
Subject Re: Please update your jenkins job configs ASAP
Date Tue, 15 Nov 2016 16:59:07 GMT
Oops, I skipped the 1.1 and 0.98 jobs, but just checked them now. (jenkins
seems super slow!)

1.1 jobs seem to be updated already with the Hadoop label and not having
the not-h2 label. [1][2] They seems like some runs have passed since the
notification had been made.

0.98 jobs are blocked on yahoo-not-h2 so I've just updated them also to use
the Hadoop label as well and they seem unblocked now.

[1] https://builds.apache.org/job/HBase-1.1-JDK7/configure
[2] https://builds.apache.org/job/HBase-1.1-JDK8/configure
[3] https://builds.apache.org/view/H-L/view/HBase/job/HBase-0.98-matrix/

On Mon, Nov 14, 2016 at 3:52 PM, Nick Dimiduk <ndimiduk@gmail.com> wrote:

> @Jon, you think I should follow your lead with 1.1 jobs?
>
> On Mon, Nov 14, 2016 at 1:21 PM, Jonathan Hsieh <jon@cloudera.com> wrote:
>
> > Looks like our hbase 1.2 and 1.3[1] jobs seemed to be running ok with the
> > Hadoop label, so I've updated the 1.4 [2] and master [3] jobs to use the
> > Hadoop label as well.
> >
> > [1] https://builds.apache.org/job/HBase-1.3-JDK8/
> > [2] https://builds.apache.org/job/HBase-1.4/
> > [3] https://builds.apache.org/job/HBase-Trunk_matrix/
> >
> > On Fri, Nov 11, 2016 at 10:37 AM, Stack <stack@duboce.net> wrote:
> >
> > > Thanks Gavin. The not-h2 label was added because our jobs were failing
> > when
> > > they ran on h2.
> > >
> > > Our jobs have just started failing w/ OOMEs (HBASE-17074).  You seeing
> > that
> > > anywhere else and if so, any input before we start trying to untangle
> (I
> > > ask you because you have more insight than we do)?
> > >
> > > Thanks,
> > > S
> > >
> > >
> > > On Thu, Nov 10, 2016 at 7:44 PM, Gavin McDonald <
> gavin@16degrees.com.au>
> > > wrote:
> > >
> > > > Hi HBasers!
> > > >
> > > > A couple of days ago I removed labels from the jenkins nodes (as
> > promised
> > > > in an earlier mail) and at the same
> > > > time I changed your builds to remove the ‘yahoo-no-h2r’ label and
> > replace
> > > > it with ‘Hadoop’.
> > > >
> > > > Looks like your jobs have reverted back to the ‘ubuntu-not-h2’ label
> > and
> > > > are now awaiting in the queue for a node that
> > > > doesn’t exist.
> > > >
> > > > Please update your jobs using whatever method (job-dsl etc) so your
> > jobs
> > > > can resume building.
> > > >
> > > > See https://cwiki.apache.org/confluence/display/INFRA/
> > > Jenkins+node+labels
> > > > <https://cwiki.apache.org/confluence/display/INFRA/
> Jenkins+node+labels
> > >
> > > > for the upto date slimmed down
> > > > label listing. As you’ll see the ‘Hadoop’ label gives you (currently
> a
> > > > minimum of) 10 nodes and choosing
> > > > (Hadoop||ubuntu) gives you 27 nodes!.
> > > >
> > > > Recap - there is NO YAHOO-NOT-H2 LABEL. It is not needed - H2 is the
> > same
> > > > as any other node.
> > > >
> > > > Thanks!
> > > >
> > > > Gav… (ASF Infra.)
> > >
> >
> >
> >
> > --
> > // Jonathan Hsieh (shay)
> > // HBase Tech Lead, Software Engineer, Cloudera
> > // jon@cloudera.com // @jmhsieh
> >
>



-- 
// Jonathan Hsieh (shay)
// HBase Tech Lead, Software Engineer, Cloudera
// jon@cloudera.com // @jmhsieh

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message