You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Kirk Lund <kl...@apache.org> on 2017/03/21 18:13:55 UTC
Blacklist asf904 for Geode nightly job
Please blacklist asf904 for the Geode nightly job. It seems to be giving
bad DNS info to our tests, causing UniversalMembershipListenerAdapterDUnitTest
to fail again. Alternatively, if someone else wants to look into the
failures in UniversalMembershipListenerAdapterDUnitTest please go ahead.
I've done all I can for the test.
Thanks,
Kirk
Re: Blacklist asf904 for Geode nightly job
Posted by Kirk Lund <kl...@apache.org>.
Unfortunately I don't know enough about DNS or more likely the internal
membership details of client/server to determine why one part of geode says
the hostname is 67.195.81.148 while another part of geode says the hostname
is asf904.
DistributedMember.getId() for a client is returning 67.195.81.148
ClientMembershipListener fires events with ClientMembershipEvent and
ClientMembershipEvent.getMemberId() is returning asf904
I think this is beyond my knowledge of JMX, management, type stuff and
requires someone with client/server membership knowledge to investigate
further. I'm not sure why DistributedMember.getId() and
ClientMembershipEvent.getMemberId() returns the same value on some asf
machines but on other machines one returns ip address while one returns a
host name. I don't really know if it's the machine that's wrong, the test
code that's wrong or something inside that client membership code.
org.apache.geode.management.UniversalMembershipListenerAdapterDUnitTest >
testSystemClientEventsInServer FAILED org.junit.ComparisonFailure:
expected:<[67.195.81.148](13093)<ec><v8>:3277...> but
was:<[asf904](13093)<ec><v8>:3277...>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at
org.apache.geode.management.UniversalMembershipListenerAdapterDUnitTest.doTestSystemClientEventsInServer(UniversalMembershipListenerAdapterDUnitTest.java:946)
at
org.apache.geode.management.UniversalMembershipListenerAdapterDUnitTest.testSystemClientEventsInServer(UniversalMembershipListenerAdapterDUnitTest.java:731)
Thanks,
Kirk
On Tue, Mar 21, 2017 at 12:01 PM, Mark Bretl <as...@gmail.com> wrote:
> Hi Kirk,
>
> It looks like the build actually ran on a machine called 'H4', which is
> designated as a Hadoop machine. I do not see why running on a Hadoop system
> would be an issue, however, I do not know the ASF infrastructure well
> enough to know why there are DNS issues.
>
> We use labels, tied to certain Jenkins nodes, to restrict where we run our
> builds, however, if a new system is added to the label, there is not much
> we can do. Maybe it is time to work worth INFRA, or some other container,
> to get a environment we can rely on all the time?
>
> --Mark
>
> On Tue, Mar 21, 2017 at 11:13 AM, Kirk Lund <kl...@apache.org> wrote:
>
> > Please blacklist asf904 for the Geode nightly job. It seems to be giving
> > bad DNS info to our tests, causing UniversalMembershipListenerAda
> > pterDUnitTest
> > to fail again. Alternatively, if someone else wants to look into the
> > failures in UniversalMembershipListenerAdapterDUnitTest please go ahead.
> > I've done all I can for the test.
> >
> > Thanks,
> > Kirk
> >
>
Re: Jenkins karma (was Re: Blacklist asf904 for Geode nightly job)
Posted by Anthony Baker <ab...@pivotal.io>.
Yea, thanks Mark!
Anthony
> On Apr 10, 2017, at 2:11 PM, Mark Bretl <mb...@apache.org> wrote:
>
> Hi Anthony,
>
> Look at that I do have karma for adding people to Jenkins. I have added you
> to Jenkins.
>
> Please let me know if you have any issues.
>
> --Mark
>
> On Mon, Apr 10, 2017 at 9:59 AM, William Markito Oliveira <
> william.markito@gmail.com> wrote:
>
>> Hi Anthony,
>>
>> My karma is also limited, sorry. I believe only Roman (or infra) can
>> change that...
>>
>> On Mon, Apr 10, 2017 at 11:46 AM, Anthony Baker <ab...@pivotal.io> wrote:
>>
>>> Anyone?
>>>
>>>> On Apr 7, 2017, at 11:32 AM, Anthony Baker <ab...@pivotal.io> wrote:
>>>>
>>>> I would like Jenkins karma so I can explore running our tests from
>>> within a docker container. William / Mark / Roman can you help me out?
>>>>
>>>> Thanks,
>>>> Anthony
>>>>
>>>>
>>>>> On Mar 21, 2017, at 3:14 PM, Anthony Baker <ab...@pivotal.io> wrote:
>>>>>
>>>>> Would be very nice to run our jenkins jobs from a docker container to
>>> avoid these environmental quirks.
>>>>>
>>>>> Anthony
>>>
>>>
>>
>>
>> --
>> ~/William
>>
Re: Jenkins karma (was Re: Blacklist asf904 for Geode nightly job)
Posted by Mark Bretl <mb...@apache.org>.
Hi Anthony,
Look at that I do have karma for adding people to Jenkins. I have added you
to Jenkins.
Please let me know if you have any issues.
--Mark
On Mon, Apr 10, 2017 at 9:59 AM, William Markito Oliveira <
william.markito@gmail.com> wrote:
> Hi Anthony,
>
> My karma is also limited, sorry. I believe only Roman (or infra) can
> change that...
>
> On Mon, Apr 10, 2017 at 11:46 AM, Anthony Baker <ab...@pivotal.io> wrote:
>
> > Anyone?
> >
> > > On Apr 7, 2017, at 11:32 AM, Anthony Baker <ab...@pivotal.io> wrote:
> > >
> > > I would like Jenkins karma so I can explore running our tests from
> > within a docker container. William / Mark / Roman can you help me out?
> > >
> > > Thanks,
> > > Anthony
> > >
> > >
> > >> On Mar 21, 2017, at 3:14 PM, Anthony Baker <ab...@pivotal.io> wrote:
> > >>
> > >> Would be very nice to run our jenkins jobs from a docker container to
> > avoid these environmental quirks.
> > >>
> > >> Anthony
> >
> >
>
>
> --
> ~/William
>
Re: Jenkins karma (was Re: Blacklist asf904 for Geode nightly job)
Posted by William Markito Oliveira <wi...@gmail.com>.
Hi Anthony,
My karma is also limited, sorry. I believe only Roman (or infra) can
change that...
On Mon, Apr 10, 2017 at 11:46 AM, Anthony Baker <ab...@pivotal.io> wrote:
> Anyone?
>
> > On Apr 7, 2017, at 11:32 AM, Anthony Baker <ab...@pivotal.io> wrote:
> >
> > I would like Jenkins karma so I can explore running our tests from
> within a docker container. William / Mark / Roman can you help me out?
> >
> > Thanks,
> > Anthony
> >
> >
> >> On Mar 21, 2017, at 3:14 PM, Anthony Baker <ab...@pivotal.io> wrote:
> >>
> >> Would be very nice to run our jenkins jobs from a docker container to
> avoid these environmental quirks.
> >>
> >> Anthony
>
>
--
~/William
Re: Jenkins karma (was Re: Blacklist asf904 for Geode nightly job)
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Mon, Apr 10, 2017 at 9:46 AM, Anthony Baker <ab...@pivotal.io> wrote:
> Anyone?
This should be done by Mark (current Chair).
Mark, can you add Anthony to the Jenkins LDAP group?
Thanks,
Roman.
Jenkins karma (was Re: Blacklist asf904 for Geode nightly job)
Posted by Anthony Baker <ab...@pivotal.io>.
Anyone?
> On Apr 7, 2017, at 11:32 AM, Anthony Baker <ab...@pivotal.io> wrote:
>
> I would like Jenkins karma so I can explore running our tests from within a docker container. William / Mark / Roman can you help me out?
>
> Thanks,
> Anthony
>
>
>> On Mar 21, 2017, at 3:14 PM, Anthony Baker <ab...@pivotal.io> wrote:
>>
>> Would be very nice to run our jenkins jobs from a docker container to avoid these environmental quirks.
>>
>> Anthony
Re: Blacklist asf904 for Geode nightly job
Posted by Anthony Baker <ab...@pivotal.io>.
I would like Jenkins karma so I can explore running our tests from within a docker container. William / Mark / Roman can you help me out?
Thanks,
Anthony
> On Mar 21, 2017, at 3:14 PM, Anthony Baker <ab...@pivotal.io> wrote:
>
> Would be very nice to run our jenkins jobs from a docker container to avoid these environmental quirks.
>
> Anthony
>
>> On Mar 21, 2017, at 12:01 PM, Mark Bretl <as...@gmail.com> wrote:
>>
>> Hi Kirk,
>>
>> It looks like the build actually ran on a machine called 'H4', which is
>> designated as a Hadoop machine. I do not see why running on a Hadoop system
>> would be an issue, however, I do not know the ASF infrastructure well
>> enough to know why there are DNS issues.
>>
>> We use labels, tied to certain Jenkins nodes, to restrict where we run our
>> builds, however, if a new system is added to the label, there is not much
>> we can do. Maybe it is time to work worth INFRA, or some other container,
>> to get a environment we can rely on all the time?
>>
>> --Mark
>>
>> On Tue, Mar 21, 2017 at 11:13 AM, Kirk Lund <kl...@apache.org> wrote:
>>
>>> Please blacklist asf904 for the Geode nightly job. It seems to be giving
>>> bad DNS info to our tests, causing UniversalMembershipListenerAda
>>> pterDUnitTest
>>> to fail again. Alternatively, if someone else wants to look into the
>>> failures in UniversalMembershipListenerAdapterDUnitTest please go ahead.
>>> I've done all I can for the test.
>>>
>>> Thanks,
>>> Kirk
>>>
>
Re: Blacklist asf904 for Geode nightly job
Posted by Anthony Baker <ab...@pivotal.io>.
Would be very nice to run our jenkins jobs from a docker container to avoid these environmental quirks.
Anthony
> On Mar 21, 2017, at 12:01 PM, Mark Bretl <as...@gmail.com> wrote:
>
> Hi Kirk,
>
> It looks like the build actually ran on a machine called 'H4', which is
> designated as a Hadoop machine. I do not see why running on a Hadoop system
> would be an issue, however, I do not know the ASF infrastructure well
> enough to know why there are DNS issues.
>
> We use labels, tied to certain Jenkins nodes, to restrict where we run our
> builds, however, if a new system is added to the label, there is not much
> we can do. Maybe it is time to work worth INFRA, or some other container,
> to get a environment we can rely on all the time?
>
> --Mark
>
> On Tue, Mar 21, 2017 at 11:13 AM, Kirk Lund <kl...@apache.org> wrote:
>
>> Please blacklist asf904 for the Geode nightly job. It seems to be giving
>> bad DNS info to our tests, causing UniversalMembershipListenerAda
>> pterDUnitTest
>> to fail again. Alternatively, if someone else wants to look into the
>> failures in UniversalMembershipListenerAdapterDUnitTest please go ahead.
>> I've done all I can for the test.
>>
>> Thanks,
>> Kirk
>>
Re: Blacklist asf904 for Geode nightly job
Posted by Mark Bretl <as...@gmail.com>.
Hi Kirk,
It looks like the build actually ran on a machine called 'H4', which is
designated as a Hadoop machine. I do not see why running on a Hadoop system
would be an issue, however, I do not know the ASF infrastructure well
enough to know why there are DNS issues.
We use labels, tied to certain Jenkins nodes, to restrict where we run our
builds, however, if a new system is added to the label, there is not much
we can do. Maybe it is time to work worth INFRA, or some other container,
to get a environment we can rely on all the time?
--Mark
On Tue, Mar 21, 2017 at 11:13 AM, Kirk Lund <kl...@apache.org> wrote:
> Please blacklist asf904 for the Geode nightly job. It seems to be giving
> bad DNS info to our tests, causing UniversalMembershipListenerAda
> pterDUnitTest
> to fail again. Alternatively, if someone else wants to look into the
> failures in UniversalMembershipListenerAdapterDUnitTest please go ahead.
> I've done all I can for the test.
>
> Thanks,
> Kirk
>