You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by Rafael Schloming <rh...@alum.mit.edu> on 2012/10/25 22:07:02 UTC

RC5

Please have a look. This one includes ken's ssl fix in addition to
everything that was in RC4:

http://people.apache.org/~rhs/qpid-proton-0.1rc5/

Re: RC5

Posted by Rafael Schloming <rh...@alum.mit.edu>.
That particular test does a DNS lookup on an invalid address, and if that
happens to take a while it can fail the way you're seeing. It will also
fail if you happen to be on one of those networks that are configured to
resolve all invalid hostnames to some kind of search engine.

--Rafael

On Thu, Oct 25, 2012 at 6:56 PM, Rob Godfrey <ro...@gmail.com>wrote:

> OK - proton-c built OK for me on Ubuntu 12.04 (32-bit) and Centos 6.3
> (32 bit)... Tests all worked fine on the Ubuntu machine.  On CentOS I
> got the following error:
>
> proton_tests.messenger.MessengerTest.testSendBogus
>
> ...................................................................................................
> start
>   server timed out
> proton_tests.messenger.MessengerTest.testSendBogus
>
> ...................................................................................................
> fail
> Error during teardown:  Traceback (most recent call last):
>     File "./proton-test", line 331, in run
>       phase()
>     File "/home/rob/qpid-proton-c-0.1/tests/proton_tests/messenger.py",
> line 45, in teardown
>       self.client.send()
>     File "/home/rob/qpid-proton-c-0.1/bindings/python/proton.py", line
> 288, in send
>       self._check(pn_messenger_send(self._mng))
>     File "/home/rob/qpid-proton-c-0.1/bindings/python/proton.py", line
> 149, in _check
>       raise exc("[%s]: %s" % (err, pn_messenger_error(self._mng)))
>   Timeout: [-7]: unable to send to address: totally-bogus-address
> (getaddrinfo: Name or service not known)
>
> all other tests passed
>
> -- Rob
>
> On 25 October 2012 22:07, Rafael Schloming <rh...@alum.mit.edu> wrote:
> > Please have a look. This one includes ken's ssl fix in addition to
> > everything that was in RC4:
> >
> > http://people.apache.org/~rhs/qpid-proton-0.1rc5/
>

Re: RC5

Posted by Rob Godfrey <ro...@gmail.com>.
OK - proton-c built OK for me on Ubuntu 12.04 (32-bit) and Centos 6.3
(32 bit)... Tests all worked fine on the Ubuntu machine.  On CentOS I
got the following error:

proton_tests.messenger.MessengerTest.testSendBogus
...................................................................................................
start
  server timed out
proton_tests.messenger.MessengerTest.testSendBogus
...................................................................................................
fail
Error during teardown:  Traceback (most recent call last):
    File "./proton-test", line 331, in run
      phase()
    File "/home/rob/qpid-proton-c-0.1/tests/proton_tests/messenger.py",
line 45, in teardown
      self.client.send()
    File "/home/rob/qpid-proton-c-0.1/bindings/python/proton.py", line
288, in send
      self._check(pn_messenger_send(self._mng))
    File "/home/rob/qpid-proton-c-0.1/bindings/python/proton.py", line
149, in _check
      raise exc("[%s]: %s" % (err, pn_messenger_error(self._mng)))
  Timeout: [-7]: unable to send to address: totally-bogus-address
(getaddrinfo: Name or service not known)

all other tests passed

-- Rob

On 25 October 2012 22:07, Rafael Schloming <rh...@alum.mit.edu> wrote:
> Please have a look. This one includes ken's ssl fix in addition to
> everything that was in RC4:
>
> http://people.apache.org/~rhs/qpid-proton-0.1rc5/

Re: RC5

Posted by Rafael Schloming <rh...@alum.mit.edu>.
This was my bad, I'll post an RC6 with the shim fixed.

--Rafael

On Thu, Oct 25, 2012 at 5:35 PM, Rajith Attapattu <ra...@gmail.com>wrote:

> We have a build failure on the java side.
> It appears the SSL tests added in Kens fix is failing.
> proton_tests.ssl.SslTest.test_client_authentication .....................
> fail
>
> We should exclude this test before we spin the final release.
>
> Rajith
>
> On Thu, Oct 25, 2012 at 5:25 PM, Ken Giusti <kg...@redhat.com> wrote:
> > mea culpa - apologies.
> >
> > However, RC5 looks pretty good on these platforms:
> >
> > Fedora 17 (64bit)
> > Debian 6 (32bit, vm)
> > Ubuntu 12.04 (32bit, vm)
> > Centos 6 (64bit, vm)
> >
> >
> > I simply did a make & install, then ran the proton test suite.   A few
> warnings during build, but all tests pass.
> >
> > The only problem platform was my Centos5 VM (32bit).  The "make all/make
> install" failed due to the php.swg file not being present.  It appears that
> the version of swig on Centos5 (1.3.29) does not include that php.swg file:
> >
> > [ 95%] Swig source
> > /home/kgiusti/work/proton/RC1/qpid-proton-c-0.1/bindings/php/php.i:4:
> Error: Unable to find 'php.swg'
> > make[2]: *** [bindings/php/phpPHP_wrap.c] Error 1
> > make[1]: *** [bindings/php/CMakeFiles/cproton.dir/all] Error 2
> > make: *** [all] Error 2
> >
> >
> > IMHO: +1 RC5, fix the Centos 5 issue in the next release.
> >
> > -K
> >
> > ----- Original Message -----
> >> Please have a look. This one includes ken's ssl fix in addition to
> >> everything that was in RC4:
> >>
> >> http://people.apache.org/~rhs/qpid-proton-0.1rc5/
> >>
>

Re: RC5

Posted by Rajith Attapattu <ra...@gmail.com>.
We have a build failure on the java side.
It appears the SSL tests added in Kens fix is failing.
proton_tests.ssl.SslTest.test_client_authentication ..................... fail

We should exclude this test before we spin the final release.

Rajith

On Thu, Oct 25, 2012 at 5:25 PM, Ken Giusti <kg...@redhat.com> wrote:
> mea culpa - apologies.
>
> However, RC5 looks pretty good on these platforms:
>
> Fedora 17 (64bit)
> Debian 6 (32bit, vm)
> Ubuntu 12.04 (32bit, vm)
> Centos 6 (64bit, vm)
>
>
> I simply did a make & install, then ran the proton test suite.   A few warnings during build, but all tests pass.
>
> The only problem platform was my Centos5 VM (32bit).  The "make all/make install" failed due to the php.swg file not being present.  It appears that the version of swig on Centos5 (1.3.29) does not include that php.swg file:
>
> [ 95%] Swig source
> /home/kgiusti/work/proton/RC1/qpid-proton-c-0.1/bindings/php/php.i:4: Error: Unable to find 'php.swg'
> make[2]: *** [bindings/php/phpPHP_wrap.c] Error 1
> make[1]: *** [bindings/php/CMakeFiles/cproton.dir/all] Error 2
> make: *** [all] Error 2
>
>
> IMHO: +1 RC5, fix the Centos 5 issue in the next release.
>
> -K
>
> ----- Original Message -----
>> Please have a look. This one includes ken's ssl fix in addition to
>> everything that was in RC4:
>>
>> http://people.apache.org/~rhs/qpid-proton-0.1rc5/
>>

Re: RC5

Posted by Ken Giusti <kg...@redhat.com>.
mea culpa - apologies.

However, RC5 looks pretty good on these platforms:

Fedora 17 (64bit)
Debian 6 (32bit, vm)
Ubuntu 12.04 (32bit, vm)
Centos 6 (64bit, vm)


I simply did a make & install, then ran the proton test suite.   A few warnings during build, but all tests pass.

The only problem platform was my Centos5 VM (32bit).  The "make all/make install" failed due to the php.swg file not being present.  It appears that the version of swig on Centos5 (1.3.29) does not include that php.swg file:

[ 95%] Swig source
/home/kgiusti/work/proton/RC1/qpid-proton-c-0.1/bindings/php/php.i:4: Error: Unable to find 'php.swg'
make[2]: *** [bindings/php/phpPHP_wrap.c] Error 1
make[1]: *** [bindings/php/CMakeFiles/cproton.dir/all] Error 2
make: *** [all] Error 2


IMHO: +1 RC5, fix the Centos 5 issue in the next release.

-K

----- Original Message -----
> Please have a look. This one includes ken's ssl fix in addition to
> everything that was in RC4:
> 
> http://people.apache.org/~rhs/qpid-proton-0.1rc5/
>