matrix item of where to run, we run on arbitrary
> nodes rather than the H* nodes. That's fine if what we intend. Historically
> the arbitrary nodes have not had enough resources to run our test suite.
>
>
> (Also the image did not come through)
>
> On Tue, Nov 15, 2016 at 11:49
e set them up so the look like this now (image is from
trunk [1])
Jon.
[1] [image: Inline image 1]
On Tue, Nov 15, 2016 at 9:13 AM, Jonathan Hsieh wrote:
> Looks like the matrix jobs -- trunk and 1.4 aren't actually running
> anything as well as the updated 0.98 jobs. This may have
ds.
>>
>> The build only took 2 min 44 sec ?
>>
>
> This is pretty much the same we are seeing with our jobs [1]. The UI
> doesn't show any configured nodes/labels, which I guess is why nothing
> runs. However it doesn't offer the option to assign nodes/labels nei
/
On Mon, Nov 14, 2016 at 3:52 PM, Nick Dimiduk wrote:
> @Jon, you think I should follow your lead with 1.1 jobs?
>
> On Mon, Nov 14, 2016 at 1:21 PM, Jonathan Hsieh wrote:
>
> > Looks like our hbase 1.2 and 1.3[1] jobs seemed to be running ok with the
> > Hadoop label, so
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!.
> >
> >
