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 > >>> > >>> > >>> > >>> >
