You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Steve Huston <sh...@riverace.com> on 2012/02/22 17:10:44 UTC
Windows test failures
Hi Alan,
I'm seeing many of the Windows tests failing this week after the build
errors were resolved. Please see:
http://www.riverace.com/CDash-1.4.2/index.php?project=qpid-cpp
Are these things you've seen and are aware of?
Thanks,
-steve
--
Steve Huston, Riverace Corporation
Total Lifecycle Support for Your Networked Applications
http://www.riverace.com
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Windows test failures
Posted by Alan Conway <ac...@redhat.com>.
On 02/23/2012 10:42 AM, Steve Huston wrote:
> Thanks, Alan! Those errors are gone today. The PYTHON missing module is
> still there but is probably an error on my part... I'll check into it
> further.
> -Steve
>
Great - shout if there's anything else that looks like it might be my fault.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: Windows test failures
Posted by Steve Huston <sh...@riverace.com>.
Thanks, Alan! Those errors are gone today. The PYTHON missing module is
still there but is probably an error on my part... I'll check into it
further.
-Steve
> -----Original Message-----
> From: Alan Conway [mailto:aconway@redhat.com]
> Sent: Wednesday, February 22, 2012 6:47 PM
> To: dev@qpid.apache.org
> Subject: RE: Windows test failures
>
> I've committed a fix for error on windows "An operation was attempted on
> something that is not a socket." An ill-advised attempt to make socket
> errors
> more informative on my part. I'm still not able to run the full set of
> tests on
> windows so I'm not sure if I've covered all of the problems.
>
>
> On Wed, 2012-02-22 at 10:48 -0600, Steve Huston wrote:
> > Right, the ipv6 test doesn't have a PowerShell script yet, and I think
> > the python missing module is a PYTHONPATH issue. The ones I was more
> > concerned with are coming from C++ code and are "operation attempted
> > on an object which is not a socket" or similar. The unit tests fails
> > with this and at least one other such as client_test.
> >
> > To run the tests under ctest control, cd to the build directory and
> >
> > ctest -R <test-expression>
> >
> > And you can start a broker (if needed) in a terminal window then run
> > the test program in the debugger.
> >
> > -Steve
> >
> > > -----Original Message-----
> > > From: Alan Conway [mailto:aconway@redhat.com]
> > > Sent: Wednesday, February 22, 2012 11:42 AM
> > > To: Steve Huston
> > > Cc: dev@qpid.apache.org
> > > Subject: Re: Windows test failures
> > >
> > > On Wed, 2012-02-22 at 10:10 -0600, Steve Huston wrote:
> > > > Hi Alan,
> > > >
> > > > I'm seeing many of the Windows tests failing this week after the
> > > > build errors were resolved. Please see:
> > > > http://www.riverace.com/CDash-1.4.2/index.php?project=qpid-cpp
> > > >
> > > > Are these things you've seen and are aware of?
> > >
> > > Nope, wasn't aware. I'll look into it as soon as I've figured out
> > > how to run the tests on windows (I confess since I was only changing
> > > EXERN decls I assumed building was enougy)
> > >
> > > Many of the failures look like they might environment problems with
> > > PATH or PYTHONPATH, e.g.:
> > >
> > > The term 'C:/qpid/trunk/qpid/cpp/src/tests/ipv6_test.ps1' is not
> > > recognized as a cmdlet, function, operable program, or script file.
> > > Verify the term and try again.
> > >
> > > Traceback (most recent call last):
> > > File "C:\qpid\trunk\qpid\cpp\src\tests
> > > \..\..\..\python/qpid-python-test",
> > > line 563, in <module>
> > > m = __import__(name, None, None, ["dummy"])
> > > File "C:\qpid\trunk\qpid\tests\src\py\qpid_tests\__init__.py",
> > > line 22, in <module>
> > > import broker_0_10, broker_0_9, broker_0_8
> > > File "C:\qpid\trunk\qpid\tests\src\py\qpid_tests\broker_0_10
> > > \__init__.py", line 38, in <module>
> > > from stats import *
> > > File "C:\qpid\trunk\qpid\tests\src\py\qpid_tests\broker_0_10
> > > \stats.py", line 24, in <module>
> > > from qpidtoollibs.broker import BrokerAgent
> > > ImportError: No module named qpidtoollibs.broker
> > >
> > >
> > > ---------------------------------------------------------------------
> > > Apache Qpid - AMQP Messaging Implementation
> > > Project: http://qpid.apache.org
> > > Use/Interact: mailto:dev-subscribe@qpid.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > Apache Qpid - AMQP Messaging Implementation
> > Project: http://qpid.apache.org
> > Use/Interact: mailto:dev-subscribe@qpid.apache.org
> >
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Windows test failures
Posted by Alan Conway <ac...@redhat.com>.
On 02/22/2012 06:46 PM, Alan Conway wrote:
> I've committed a fix for error on windows "An operation was attempted on
> something that is not a socket." An ill-advised attempt to make socket
> errors more informative on my part. I'm still not able to run the full
> set of tests on windows so I'm not sure if I've covered all of the
> problems.
>
How do things look to you after this revision? It fixes the not-a-socket problem:
------------------------------------------------------------------------
r1292587 | aconway | 2012-02-22 18:46:48 -0500 (Wed, 22 Feb 2012) | 2 lines
NO-JIRA: Fix error on windows "An operation was attempted on something that is
not a socket."
------------------------------------------------------------------------
> On Wed, 2012-02-22 at 10:48 -0600, Steve Huston wrote:
>> Right, the ipv6 test doesn't have a PowerShell script yet, and I think the
>> python missing module is a PYTHONPATH issue. The ones I was more concerned
>> with are coming from C++ code and are "operation attempted on an object
>> which is not a socket" or similar. The unit tests fails with this and at
>> least one other such as client_test.
>>
>> To run the tests under ctest control, cd to the build directory and
>>
>> ctest -R<test-expression>
>
I'm still having a lot of trouble with ctest. It will run a test for me about
half the time, and just hang the other half. When it runs it takes an
inexplicably long time, e.g. qpid-client-test took 56 seconds to run. If I run
it by hand it's instantaneous.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: Windows test failures
Posted by Alan Conway <ac...@redhat.com>.
I've committed a fix for error on windows "An operation was attempted on
something that is not a socket." An ill-advised attempt to make socket
errors more informative on my part. I'm still not able to run the full
set of tests on windows so I'm not sure if I've covered all of the
problems.
On Wed, 2012-02-22 at 10:48 -0600, Steve Huston wrote:
> Right, the ipv6 test doesn't have a PowerShell script yet, and I think the
> python missing module is a PYTHONPATH issue. The ones I was more concerned
> with are coming from C++ code and are "operation attempted on an object
> which is not a socket" or similar. The unit tests fails with this and at
> least one other such as client_test.
>
> To run the tests under ctest control, cd to the build directory and
>
> ctest -R <test-expression>
>
> And you can start a broker (if needed) in a terminal window then run the
> test program in the debugger.
>
> -Steve
>
> > -----Original Message-----
> > From: Alan Conway [mailto:aconway@redhat.com]
> > Sent: Wednesday, February 22, 2012 11:42 AM
> > To: Steve Huston
> > Cc: dev@qpid.apache.org
> > Subject: Re: Windows test failures
> >
> > On Wed, 2012-02-22 at 10:10 -0600, Steve Huston wrote:
> > > Hi Alan,
> > >
> > > I'm seeing many of the Windows tests failing this week after the build
> > > errors were resolved. Please see:
> > > http://www.riverace.com/CDash-1.4.2/index.php?project=qpid-cpp
> > >
> > > Are these things you've seen and are aware of?
> >
> > Nope, wasn't aware. I'll look into it as soon as I've figured out how to
> > run the
> > tests on windows (I confess since I was only changing EXERN decls I
> > assumed
> > building was enougy)
> >
> > Many of the failures look like they might environment problems with PATH
> > or PYTHONPATH, e.g.:
> >
> > The term 'C:/qpid/trunk/qpid/cpp/src/tests/ipv6_test.ps1' is not
> > recognized
> > as a cmdlet, function, operable program, or script file.
> > Verify the term and try again.
> >
> > Traceback (most recent call last):
> > File "C:\qpid\trunk\qpid\cpp\src\tests
> > \..\..\..\python/qpid-python-test",
> > line 563, in <module>
> > m = __import__(name, None, None, ["dummy"])
> > File "C:\qpid\trunk\qpid\tests\src\py\qpid_tests\__init__.py", line 22,
> > in
> > <module>
> > import broker_0_10, broker_0_9, broker_0_8
> > File "C:\qpid\trunk\qpid\tests\src\py\qpid_tests\broker_0_10
> > \__init__.py", line 38, in <module>
> > from stats import *
> > File "C:\qpid\trunk\qpid\tests\src\py\qpid_tests\broker_0_10
> > \stats.py", line 24, in <module>
> > from qpidtoollibs.broker import BrokerAgent
> > ImportError: No module named qpidtoollibs.broker
> >
> >
> > ---------------------------------------------------------------------
> > Apache Qpid - AMQP Messaging Implementation
> > Project: http://qpid.apache.org
> > Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: Windows test failures
Posted by Steve Huston <sh...@riverace.com>.
Right, the ipv6 test doesn't have a PowerShell script yet, and I think the
python missing module is a PYTHONPATH issue. The ones I was more concerned
with are coming from C++ code and are "operation attempted on an object
which is not a socket" or similar. The unit tests fails with this and at
least one other such as client_test.
To run the tests under ctest control, cd to the build directory and
ctest -R <test-expression>
And you can start a broker (if needed) in a terminal window then run the
test program in the debugger.
-Steve
> -----Original Message-----
> From: Alan Conway [mailto:aconway@redhat.com]
> Sent: Wednesday, February 22, 2012 11:42 AM
> To: Steve Huston
> Cc: dev@qpid.apache.org
> Subject: Re: Windows test failures
>
> On Wed, 2012-02-22 at 10:10 -0600, Steve Huston wrote:
> > Hi Alan,
> >
> > I'm seeing many of the Windows tests failing this week after the build
> > errors were resolved. Please see:
> > http://www.riverace.com/CDash-1.4.2/index.php?project=qpid-cpp
> >
> > Are these things you've seen and are aware of?
>
> Nope, wasn't aware. I'll look into it as soon as I've figured out how to
> run the
> tests on windows (I confess since I was only changing EXERN decls I
> assumed
> building was enougy)
>
> Many of the failures look like they might environment problems with PATH
> or PYTHONPATH, e.g.:
>
> The term 'C:/qpid/trunk/qpid/cpp/src/tests/ipv6_test.ps1' is not
> recognized
> as a cmdlet, function, operable program, or script file.
> Verify the term and try again.
>
> Traceback (most recent call last):
> File "C:\qpid\trunk\qpid\cpp\src\tests
> \..\..\..\python/qpid-python-test",
> line 563, in <module>
> m = __import__(name, None, None, ["dummy"])
> File "C:\qpid\trunk\qpid\tests\src\py\qpid_tests\__init__.py", line 22,
> in
> <module>
> import broker_0_10, broker_0_9, broker_0_8
> File "C:\qpid\trunk\qpid\tests\src\py\qpid_tests\broker_0_10
> \__init__.py", line 38, in <module>
> from stats import *
> File "C:\qpid\trunk\qpid\tests\src\py\qpid_tests\broker_0_10
> \stats.py", line 24, in <module>
> from qpidtoollibs.broker import BrokerAgent
> ImportError: No module named qpidtoollibs.broker
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Windows test failures
Posted by Alan Conway <ac...@redhat.com>.
On Wed, 2012-02-22 at 10:10 -0600, Steve Huston wrote:
> Hi Alan,
>
> I'm seeing many of the Windows tests failing this week after the build
> errors were resolved. Please see:
> http://www.riverace.com/CDash-1.4.2/index.php?project=qpid-cpp
>
> Are these things you've seen and are aware of?
Nope, wasn't aware. I'll look into it as soon as I've figured out how to
run the tests on windows (I confess since I was only changing EXERN
decls I assumed building was enougy)
Many of the failures look like they might environment problems with PATH
or PYTHONPATH, e.g.:
The term 'C:/qpid/trunk/qpid/cpp/src/tests/ipv6_test.ps1' is not
recognized as a cmdlet, function, operable program, or script file.
Verify the term and try again.
Traceback (most recent call last):
File "C:\qpid\trunk\qpid\cpp\src\tests
\..\..\..\python/qpid-python-test", line 563, in <module>
m = __import__(name, None, None, ["dummy"])
File "C:\qpid\trunk\qpid\tests\src\py\qpid_tests\__init__.py", line
22, in <module>
import broker_0_10, broker_0_9, broker_0_8
File "C:\qpid\trunk\qpid\tests\src\py\qpid_tests\broker_0_10
\__init__.py", line 38, in <module>
from stats import *
File "C:\qpid\trunk\qpid\tests\src\py\qpid_tests\broker_0_10
\stats.py", line 24, in <module>
from qpidtoollibs.broker import BrokerAgent
ImportError: No module named qpidtoollibs.broker
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org