Re: Please update your jenkins job configs ASAP

2016-11-15 Thread Gav
fwiw I too had seen the 'disappearance' of the 'slave' configuration of the matrix jobs. Nothing to do with what I have been working on, this stopped working a while ago. I have commented on a Jenkins jira ticket about it, no response so far. Gav... On Wed, Nov 16, 2016 at 6:24 AM, Jonathan Hs

Re: Please update your jenkins job configs ASAP

2016-11-15 Thread Jonathan Hsieh
I see. I had assumed that setting the label expression constraint in the "advance project options" would take care of that but when I looked they do not. The problem actually was that they were using "slave" instead of "Label Expression". After correcting that, the matrix jobs seems to be build

Re: Please update your jenkins job configs ASAP

2016-11-15 Thread Sean Busbey
without the configuration 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 AM,

Re: Please update your jenkins job configs ASAP

2016-11-15 Thread Jonathan Hsieh
Ok, I've fixed the matrix jobs for 0.98, 1.4, and trunk builds are fixed and running against appropriate JDKs now. The fix was to removed the "Slave" Configuration matrix item (that was configured in the advanced options), and only have the JDK configuration matrix items. I've set them up so the l

Re: Please update your jenkins job configs ASAP

2016-11-15 Thread Jonathan Hsieh
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 something to do with the JDK labels that were also updated recently[1]. Maybe this is related to the "space in a matrix label name" problem that caused us to change 1.2, a

Re: Please update your jenkins job configs ASAP

2016-11-15 Thread Jonathan Hsieh
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 yaho

Re: Please update your jenkins job configs ASAP

2016-11-15 Thread Michael Dürig
Hi, On 15.11.16 5:05 , Ted Yu wrote: Looking at a reportedly successful build: https://builds.apache.org/job/HBase-1.4/533/console I don't see the JDK 1.7 / 1.8 builds. 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

Re: Please update your jenkins job configs ASAP

2016-11-14 Thread Ted Yu
Looking at a reportedly successful build: https://builds.apache.org/job/HBase-1.4/533/console I don't see the JDK 1.7 / 1.8 builds. The build only took 2 min 44 sec ? On Mon, Nov 14, 2016 at 2:51 PM, Ted Yu wrote: > We used to have JDK 1.8 build named like this: > > https://builds.apache.org/j

Re: Please update your jenkins job configs ASAP

2016-11-14 Thread Nick Dimiduk
@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 I've updated the 1.4 [2] and master [3] jobs to use the > Hadoop label as well. > > [1] h

Re: Please update your jenkins job configs ASAP

2016-11-14 Thread Ted Yu
We used to have JDK 1.8 build named like this: https://builds.apache.org/job/HBase-Trunk_matrix/jdk=JDK%201.8%20(latest),label=yahoo-not-h2/ However, in the latest build: https://builds.apache.org/job/HBase-TRUNK_matrix/1947/console I don't see any JDK 1.8 build - it seemed that no actual build

Re: Please update your jenkins job configs ASAP

2016-11-14 Thread Jonathan Hsieh
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/

Re: Please update your jenkins job configs ASAP

2016-11-13 Thread 张铎
https://builds.apache.org/job/PreCommit-HBASE-Build/4428/consoleFull This one was executed on H18 but still failed because of OOM, so I guess the problem is not H2? 2016-11-12 2:37 GMT+08:00 Stack : > Thanks Gavin. The not-h2 label was added because our jobs were failing when > they ran on h2. >

Re: Please update your jenkins job configs ASAP

2016-11-11 Thread Stack
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)? Thank

Re: Please update your Jenkins job configs ASAP

2016-11-10 Thread Christopher
Hi Gav, Thanks for the heads up. I didn't see any of our jobs using that label. However, I did make sure all ours changed to (Hadoop||ubuntu) and aborted a currently running build, to make sure that its next run used these nodes. On Thu, Nov 10, 2016 at 10:31 PM Gavin McDonald wrote: > Hi Accum

Please update your jenkins job configs ASAP

2016-11-10 Thread Gavin McDonald
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

Please update your Jenkins job configs ASAP

2016-11-10 Thread Gavin McDonald
Hi Accumulo devs! 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-not-h2’ label and replace it with ‘Hadoop’. Looks like your jobs have reverted back to the ‘yahoo-not-h2’ label and are