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 <ga...@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.)
