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 Hsieh <[email protected]> wrote: > 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 building > on the proper machines now. > > I've updated 0.98, 1.4 and master matrix jobs. Hopefully this will get our > jobs back in business. Will check again later today. > > Jon. > > On Tue, Nov 15, 2016 at 11:01 AM, Sean Busbey <[email protected]> wrote: > > > 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, Jonathan Hsieh <[email protected]> > wrote: > > > > > 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 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 <[email protected]> > > 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 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, and 1.3 into separate jobs? (we have one good run in our > > >> history of 0.98 using the now removed latest1.6, latest1.7 labels. [2] > > >> > > >> Jon > > >> > > >> [1] https://cwiki.apache.org/confluence/display/INFRA/JDK+Instal > > >> lation+Matrix > > >> [2] https://builds.apache.org/view/H-L/view/HBase/job/HBase- > > >> 0.98-matrix/369/ > > >> > > >> On Tue, Nov 15, 2016 at 12:48 AM, Michael Dürig <[email protected]> > > >> wrote: > > >> > > >>> > > >>> 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 configured nodes/labels, which I guess is why > nothing > > >>> runs. However it doesn't offer the option to assign nodes/labels > > neither. > > >>> > > >>> Michael > > >>> > > >>> > > >>> [1] http://markmail.org/message/zteyrxolwl46jcfh > > >>> > > >> > > >> > > >> > > >> -- > > >> // Jonathan Hsieh (shay) > > >> // HBase Tech Lead, Software Engineer, Cloudera > > >> // [email protected] // @jmhsieh > > >> > > >> > > > > > > > > > > > > -- > > > // Jonathan Hsieh (shay) > > > // HBase Tech Lead, Software Engineer, Cloudera > > > // [email protected] // @jmhsieh > > > > > > > > > > > > -- > // Jonathan Hsieh (shay) > // HBase Tech Lead, Software Engineer, Cloudera > // [email protected] // @jmhsieh > -- Gav...
