You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by Andor Molnar <an...@cloudera.com.INVALID> on 2019/02/18 10:20:41 UTC
Test failure on branch-3.4 Java 11 build
Hi team,
I cannot repro the build error which has been happening since I applied the
following patch:
https://github.com/apache/zookeeper/commit/e22883c6d2f6e9068e2105fc072d9b6a39ac9a2d
It should not have anything to do with testing and the error message
doesn't make sense to me either:
java.rmi.ConnectException: Connection refused to host: 67.195.81.178;
nested exception is:
java.net.ConnectException: Connection refused (Connection refused)
It looks like somehow related to JMX connection in the tearDown() method of
various tests.
However, tests work just fine for me on my Mac and CentOS 7.5.
Regards,
Andor
Re: Test failure on branch-3.4 Java 11 build
Posted by Andor Molnar <an...@cloudera.com.INVALID>.
Got it.
On Wed, Feb 20, 2019 at 7:56 AM Enrico Olivelli <eo...@gmail.com> wrote:
> Il giorno mer 20 feb 2019, 07:43 Andor Molnar <an...@cloudera.com.invalid>
> ha scritto:
>
> > "That patch seems unrelated." - Why do you think that?
> >
>
> This one I mean
>
>
> https://github.com/apache/zookeeper/commit/e22883c6d2f6e9068e2105fc072d9b6a39ac9a2d
>
> It's about build.xml
> No change around network/jmx/java
>
> Enrico
>
>
> >
> > On Tue, Feb 19, 2019 at 10:30 PM Enrico Olivelli <eo...@gmail.com>
> > wrote:
> >
> > > Can we read JMX beans without using the network ?
> > >
> > > Btw That patch seems unrelated.
> > >
> > > Enrico
> > >
> > > Il giorno mar 19 feb 2019, 22:26 Andor Molnár <an...@apache.org> ha
> > > scritto:
> > >
> > > > The build was successful (red, but different error) on H31 again
> > without
> > > > any modification.
> > > >
> > > > Now what? :)
> > > >
> > > >
> > > > Andor
> > > >
> > > >
> > > >
> > > >
> > > > On 2/18/19 11:40, Andor Molnar wrote:
> > > > > Infra ticket raised:
> > > > >
> > > > > https://issues.apache.org/jira/browse/INFRA-17866
> > > > >
> > > > > I'll continue with the release procedure, since the build works for
> > me
> > > > > locally.
> > > > >
> > > > > Andor
> > > > >
> > > > >
> > > > >
> > > > > On Mon, Feb 18, 2019 at 11:30 AM Andor Molnar <an...@cloudera.com>
> > > > wrote:
> > > > >
> > > > >> Not my patch. Something has been misconfigured on H31:
> > > > >>
> > > > >> Build Duration Agent
> > > > >> Failed #231 1 hr 9 min H31
> > > > >> Failed #230 1 hr 10 min H31
> > > > >> Failed #229 1 hr 10 min H31
> > > > >> Success #228 30 min H14
> > > > >> Success #227 30 min H2
> > > > >> Failed #226 1 hr 9 min H31
> > > > >> Success #225 32 min H2
> > > > >> Failed #224 31 min H39
> > > > >> Success #223 42 min H31
> > > > >> ...
> > > > >>
> > > > >> It worked with #223 on 9 Feb and failed with #226 on 12 Feb.
> > > > >>
> > > > >> Andor
> > > > >>
> > > > >>
> > > > >>
> > > > >> On Mon, Feb 18, 2019 at 11:20 AM Andor Molnar <andor@cloudera.com
> >
> > > > wrote:
> > > > >>
> > > > >>> Hi team,
> > > > >>>
> > > > >>> I cannot repro the build error which has been happening since I
> > > applied
> > > > >>> the following patch:
> > > > >>>
> > > > >>>
> > > >
> > >
> >
> https://github.com/apache/zookeeper/commit/e22883c6d2f6e9068e2105fc072d9b6a39ac9a2d
> > > > >>>
> > > > >>> It should not have anything to do with testing and the error
> > message
> > > > >>> doesn't make sense to me either:
> > > > >>>
> > > > >>> java.rmi.ConnectException: Connection refused to host:
> > 67.195.81.178;
> > > > nested exception is:
> > > > >>> java.net.ConnectException: Connection refused (Connection
> > > refused)
> > > > >>>
> > > > >>>
> > > > >>> It looks like somehow related to JMX connection in the tearDown()
> > > > method
> > > > >>> of various tests.
> > > > >>> However, tests work just fine for me on my Mac and CentOS 7.5.
> > > > >>>
> > > > >>> Regards,
> > > > >>> Andor
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>>
> > > >
> > >
> >
>
Re: Test failure on branch-3.4 Java 11 build
Posted by Enrico Olivelli <eo...@gmail.com>.
Il giorno mer 20 feb 2019, 07:43 Andor Molnar <an...@cloudera.com.invalid>
ha scritto:
> "That patch seems unrelated." - Why do you think that?
>
This one I mean
https://github.com/apache/zookeeper/commit/e22883c6d2f6e9068e2105fc072d9b6a39ac9a2d
It's about build.xml
No change around network/jmx/java
Enrico
>
> On Tue, Feb 19, 2019 at 10:30 PM Enrico Olivelli <eo...@gmail.com>
> wrote:
>
> > Can we read JMX beans without using the network ?
> >
> > Btw That patch seems unrelated.
> >
> > Enrico
> >
> > Il giorno mar 19 feb 2019, 22:26 Andor Molnár <an...@apache.org> ha
> > scritto:
> >
> > > The build was successful (red, but different error) on H31 again
> without
> > > any modification.
> > >
> > > Now what? :)
> > >
> > >
> > > Andor
> > >
> > >
> > >
> > >
> > > On 2/18/19 11:40, Andor Molnar wrote:
> > > > Infra ticket raised:
> > > >
> > > > https://issues.apache.org/jira/browse/INFRA-17866
> > > >
> > > > I'll continue with the release procedure, since the build works for
> me
> > > > locally.
> > > >
> > > > Andor
> > > >
> > > >
> > > >
> > > > On Mon, Feb 18, 2019 at 11:30 AM Andor Molnar <an...@cloudera.com>
> > > wrote:
> > > >
> > > >> Not my patch. Something has been misconfigured on H31:
> > > >>
> > > >> Build Duration Agent
> > > >> Failed #231 1 hr 9 min H31
> > > >> Failed #230 1 hr 10 min H31
> > > >> Failed #229 1 hr 10 min H31
> > > >> Success #228 30 min H14
> > > >> Success #227 30 min H2
> > > >> Failed #226 1 hr 9 min H31
> > > >> Success #225 32 min H2
> > > >> Failed #224 31 min H39
> > > >> Success #223 42 min H31
> > > >> ...
> > > >>
> > > >> It worked with #223 on 9 Feb and failed with #226 on 12 Feb.
> > > >>
> > > >> Andor
> > > >>
> > > >>
> > > >>
> > > >> On Mon, Feb 18, 2019 at 11:20 AM Andor Molnar <an...@cloudera.com>
> > > wrote:
> > > >>
> > > >>> Hi team,
> > > >>>
> > > >>> I cannot repro the build error which has been happening since I
> > applied
> > > >>> the following patch:
> > > >>>
> > > >>>
> > >
> >
> https://github.com/apache/zookeeper/commit/e22883c6d2f6e9068e2105fc072d9b6a39ac9a2d
> > > >>>
> > > >>> It should not have anything to do with testing and the error
> message
> > > >>> doesn't make sense to me either:
> > > >>>
> > > >>> java.rmi.ConnectException: Connection refused to host:
> 67.195.81.178;
> > > nested exception is:
> > > >>> java.net.ConnectException: Connection refused (Connection
> > refused)
> > > >>>
> > > >>>
> > > >>> It looks like somehow related to JMX connection in the tearDown()
> > > method
> > > >>> of various tests.
> > > >>> However, tests work just fine for me on my Mac and CentOS 7.5.
> > > >>>
> > > >>> Regards,
> > > >>> Andor
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > >
> >
>
Re: Test failure on branch-3.4 Java 11 build
Posted by Andor Molnar <an...@cloudera.com.INVALID>.
"That patch seems unrelated." - Why do you think that?
On Tue, Feb 19, 2019 at 10:30 PM Enrico Olivelli <eo...@gmail.com>
wrote:
> Can we read JMX beans without using the network ?
>
> Btw That patch seems unrelated.
>
> Enrico
>
> Il giorno mar 19 feb 2019, 22:26 Andor Molnár <an...@apache.org> ha
> scritto:
>
> > The build was successful (red, but different error) on H31 again without
> > any modification.
> >
> > Now what? :)
> >
> >
> > Andor
> >
> >
> >
> >
> > On 2/18/19 11:40, Andor Molnar wrote:
> > > Infra ticket raised:
> > >
> > > https://issues.apache.org/jira/browse/INFRA-17866
> > >
> > > I'll continue with the release procedure, since the build works for me
> > > locally.
> > >
> > > Andor
> > >
> > >
> > >
> > > On Mon, Feb 18, 2019 at 11:30 AM Andor Molnar <an...@cloudera.com>
> > wrote:
> > >
> > >> Not my patch. Something has been misconfigured on H31:
> > >>
> > >> Build Duration Agent
> > >> Failed #231 1 hr 9 min H31
> > >> Failed #230 1 hr 10 min H31
> > >> Failed #229 1 hr 10 min H31
> > >> Success #228 30 min H14
> > >> Success #227 30 min H2
> > >> Failed #226 1 hr 9 min H31
> > >> Success #225 32 min H2
> > >> Failed #224 31 min H39
> > >> Success #223 42 min H31
> > >> ...
> > >>
> > >> It worked with #223 on 9 Feb and failed with #226 on 12 Feb.
> > >>
> > >> Andor
> > >>
> > >>
> > >>
> > >> On Mon, Feb 18, 2019 at 11:20 AM Andor Molnar <an...@cloudera.com>
> > wrote:
> > >>
> > >>> Hi team,
> > >>>
> > >>> I cannot repro the build error which has been happening since I
> applied
> > >>> the following patch:
> > >>>
> > >>>
> >
> https://github.com/apache/zookeeper/commit/e22883c6d2f6e9068e2105fc072d9b6a39ac9a2d
> > >>>
> > >>> It should not have anything to do with testing and the error message
> > >>> doesn't make sense to me either:
> > >>>
> > >>> java.rmi.ConnectException: Connection refused to host: 67.195.81.178;
> > nested exception is:
> > >>> java.net.ConnectException: Connection refused (Connection
> refused)
> > >>>
> > >>>
> > >>> It looks like somehow related to JMX connection in the tearDown()
> > method
> > >>> of various tests.
> > >>> However, tests work just fine for me on my Mac and CentOS 7.5.
> > >>>
> > >>> Regards,
> > >>> Andor
> > >>>
> > >>>
> > >>>
> > >>>
> >
>
Re: Test failure on branch-3.4 Java 11 build
Posted by Enrico Olivelli <eo...@gmail.com>.
Can we read JMX beans without using the network ?
Btw That patch seems unrelated.
Enrico
Il giorno mar 19 feb 2019, 22:26 Andor Molnár <an...@apache.org> ha scritto:
> The build was successful (red, but different error) on H31 again without
> any modification.
>
> Now what? :)
>
>
> Andor
>
>
>
>
> On 2/18/19 11:40, Andor Molnar wrote:
> > Infra ticket raised:
> >
> > https://issues.apache.org/jira/browse/INFRA-17866
> >
> > I'll continue with the release procedure, since the build works for me
> > locally.
> >
> > Andor
> >
> >
> >
> > On Mon, Feb 18, 2019 at 11:30 AM Andor Molnar <an...@cloudera.com>
> wrote:
> >
> >> Not my patch. Something has been misconfigured on H31:
> >>
> >> Build Duration Agent
> >> Failed #231 1 hr 9 min H31
> >> Failed #230 1 hr 10 min H31
> >> Failed #229 1 hr 10 min H31
> >> Success #228 30 min H14
> >> Success #227 30 min H2
> >> Failed #226 1 hr 9 min H31
> >> Success #225 32 min H2
> >> Failed #224 31 min H39
> >> Success #223 42 min H31
> >> ...
> >>
> >> It worked with #223 on 9 Feb and failed with #226 on 12 Feb.
> >>
> >> Andor
> >>
> >>
> >>
> >> On Mon, Feb 18, 2019 at 11:20 AM Andor Molnar <an...@cloudera.com>
> wrote:
> >>
> >>> Hi team,
> >>>
> >>> I cannot repro the build error which has been happening since I applied
> >>> the following patch:
> >>>
> >>>
> https://github.com/apache/zookeeper/commit/e22883c6d2f6e9068e2105fc072d9b6a39ac9a2d
> >>>
> >>> It should not have anything to do with testing and the error message
> >>> doesn't make sense to me either:
> >>>
> >>> java.rmi.ConnectException: Connection refused to host: 67.195.81.178;
> nested exception is:
> >>> java.net.ConnectException: Connection refused (Connection refused)
> >>>
> >>>
> >>> It looks like somehow related to JMX connection in the tearDown()
> method
> >>> of various tests.
> >>> However, tests work just fine for me on my Mac and CentOS 7.5.
> >>>
> >>> Regards,
> >>> Andor
> >>>
> >>>
> >>>
> >>>
>
Re: Test failure on branch-3.4 Java 11 build
Posted by Andor Molnár <an...@apache.org>.
The build was successful (red, but different error) on H31 again without
any modification.
Now what? :)
Andor
On 2/18/19 11:40, Andor Molnar wrote:
> Infra ticket raised:
>
> https://issues.apache.org/jira/browse/INFRA-17866
>
> I'll continue with the release procedure, since the build works for me
> locally.
>
> Andor
>
>
>
> On Mon, Feb 18, 2019 at 11:30 AM Andor Molnar <an...@cloudera.com> wrote:
>
>> Not my patch. Something has been misconfigured on H31:
>>
>> Build Duration Agent
>> Failed #231 1 hr 9 min H31
>> Failed #230 1 hr 10 min H31
>> Failed #229 1 hr 10 min H31
>> Success #228 30 min H14
>> Success #227 30 min H2
>> Failed #226 1 hr 9 min H31
>> Success #225 32 min H2
>> Failed #224 31 min H39
>> Success #223 42 min H31
>> ...
>>
>> It worked with #223 on 9 Feb and failed with #226 on 12 Feb.
>>
>> Andor
>>
>>
>>
>> On Mon, Feb 18, 2019 at 11:20 AM Andor Molnar <an...@cloudera.com> wrote:
>>
>>> Hi team,
>>>
>>> I cannot repro the build error which has been happening since I applied
>>> the following patch:
>>>
>>> https://github.com/apache/zookeeper/commit/e22883c6d2f6e9068e2105fc072d9b6a39ac9a2d
>>>
>>> It should not have anything to do with testing and the error message
>>> doesn't make sense to me either:
>>>
>>> java.rmi.ConnectException: Connection refused to host: 67.195.81.178; nested exception is:
>>> java.net.ConnectException: Connection refused (Connection refused)
>>>
>>>
>>> It looks like somehow related to JMX connection in the tearDown() method
>>> of various tests.
>>> However, tests work just fine for me on my Mac and CentOS 7.5.
>>>
>>> Regards,
>>> Andor
>>>
>>>
>>>
>>>
Re: Test failure on branch-3.4 Java 11 build
Posted by Andor Molnar <an...@cloudera.com.INVALID>.
Infra ticket raised:
https://issues.apache.org/jira/browse/INFRA-17866
I'll continue with the release procedure, since the build works for me
locally.
Andor
On Mon, Feb 18, 2019 at 11:30 AM Andor Molnar <an...@cloudera.com> wrote:
> Not my patch. Something has been misconfigured on H31:
>
> Build Duration Agent
> Failed #231 1 hr 9 min H31
> Failed #230 1 hr 10 min H31
> Failed #229 1 hr 10 min H31
> Success #228 30 min H14
> Success #227 30 min H2
> Failed #226 1 hr 9 min H31
> Success #225 32 min H2
> Failed #224 31 min H39
> Success #223 42 min H31
> ...
>
> It worked with #223 on 9 Feb and failed with #226 on 12 Feb.
>
> Andor
>
>
>
> On Mon, Feb 18, 2019 at 11:20 AM Andor Molnar <an...@cloudera.com> wrote:
>
>> Hi team,
>>
>> I cannot repro the build error which has been happening since I applied
>> the following patch:
>>
>> https://github.com/apache/zookeeper/commit/e22883c6d2f6e9068e2105fc072d9b6a39ac9a2d
>>
>> It should not have anything to do with testing and the error message
>> doesn't make sense to me either:
>>
>> java.rmi.ConnectException: Connection refused to host: 67.195.81.178; nested exception is:
>> java.net.ConnectException: Connection refused (Connection refused)
>>
>>
>> It looks like somehow related to JMX connection in the tearDown() method
>> of various tests.
>> However, tests work just fine for me on my Mac and CentOS 7.5.
>>
>> Regards,
>> Andor
>>
>>
>>
>>
Re: Test failure on branch-3.4 Java 11 build
Posted by Andor Molnar <an...@cloudera.com.INVALID>.
Not my patch. Something has been misconfigured on H31:
Build Duration Agent
Failed #231 1 hr 9 min H31
Failed #230 1 hr 10 min H31
Failed #229 1 hr 10 min H31
Success #228 30 min H14
Success #227 30 min H2
Failed #226 1 hr 9 min H31
Success #225 32 min H2
Failed #224 31 min H39
Success #223 42 min H31
...
It worked with #223 on 9 Feb and failed with #226 on 12 Feb.
Andor
On Mon, Feb 18, 2019 at 11:20 AM Andor Molnar <an...@cloudera.com> wrote:
> Hi team,
>
> I cannot repro the build error which has been happening since I applied
> the following patch:
>
> https://github.com/apache/zookeeper/commit/e22883c6d2f6e9068e2105fc072d9b6a39ac9a2d
>
> It should not have anything to do with testing and the error message
> doesn't make sense to me either:
>
> java.rmi.ConnectException: Connection refused to host: 67.195.81.178; nested exception is:
> java.net.ConnectException: Connection refused (Connection refused)
>
>
> It looks like somehow related to JMX connection in the tearDown() method
> of various tests.
> However, tests work just fine for me on my Mac and CentOS 7.5.
>
> Regards,
> Andor
>
>
>
>