You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Rabih M <ra...@gmail.com> on 2016/05/18 14:54:29 UTC
Qpid C++ 0.34 unit tests are failing with visual studio 2013
Hello,
I compiled the Qpid C++ code on windows using visual studio 2013.
I have some unit tests failures, I tried to debug but it is not obvious to
find the root cause.
In qpid-client-test: The client is not able to connect to the qpid broker.
This the output I am getting:
...
test 1
Start 1: qpid-client-test
1: Test command: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
D:/qpid-cpp-0.34/qpid-cpp-0.34/qpid/cpp/src/tests/run_test.ps1 -buildDir
D:/qpid-cpp-0.34/qpid-cpp-0.34/qpid/cpp/build-dir -startBroker --
D:/qpid-cpp-0.34/qpid-cpp-0.34/qpid/cpp/build-dir/src/tests/qpid-client-test.exe
1: Test timeout computed to be: 1500
1: 2016-05-18 16:46:39 [Broker] notice Broker (pid=10372) start-up
1: 2016-05-18 16:46:39 [Broker] notice SASL disabled: No Authentication
Performed
1: 2016-05-18 16:46:39 [Security] notice Listening for SSL connections on
TCP port 5671
1: 2016-05-18 16:46:39 [Network] notice Listening on TCP/TCP6 port 21077
1: 2016-05-18 16:46:40 [Network] warning Connect failed: No connection
could be made because the target machine actively refused it. :
localhost:21077
(D:\qpid-cpp-0.34\qpid-cpp-0.34\qpid\cpp\src\qpid\sys\windows\WinSocket.cpp:164)
1: Connection closed
1: WARNING: suspicious log entries in
\nD:\qpid-cpp-0.34\qpid-cpp-0.34\qpid\cpp\build-dir\src\tests\qpid-client-test.log:1:2016-05-18
16:46:40 [Network] warning Connect failed: No connection could be made
because the target machine actively refused it. : localhost:21077
(D:\qpid-cpp-0.34\qpid-cpp-0.34\qpid\cpp\src\qpid\sys\windows\WinSocket.cpp:164)
1: 2016-05-18 16:46:40 [Broker] notice Broker (pid=10372) shut-down
1/1 Test #1: qpid-client-test .................***Failed 2.15 sec
Did anyone encountered this error before?
The firewall on the machine is off. And I verified using netstat that the
port 21077 was open and listening.
Thanks,
Rabih
RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Adel Boutros <ad...@live.com>.
I agree with Andrew that having ${PYTHON_EXECUTABLE} is better than relying on external system configuration or simply adding "python". That way you can also change the fix I proposed for CTEST_CUSTOM_PRE_TEST to become "set(CTEST_CUSTOM_PRE_TEST "${PYTHON_EXECUTABLE} ${CMAKE_BINARY_DIR}/src/tests/check_dependencies.py")"
Regards,Adel
> From: adelboutros@live.com
> To: users@qpid.apache.org
> Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> Date: Thu, 26 May 2016 17:38:04 +0200
>
> Hello Justin,
> I took the code from the trunk and started compiling and testing. I already have 2 issues to signal:There is a script launched "check_dependencies.py" in ctest directly. It is defined in CTestCustom.cmake. The issue is that if on my machine ".py" programs are configured to open in notepad, then the tests will fail. I propose to add the keyword"python" before the name of the script and set the correct python in the PATH environment variable. This way I can explicitly define which python version I want to use. So the line to change becomes "set(CTEST_CUSTOM_PRE_TEST "python ${CMAKE_BINARY_DIR}/src/tests/check_dependencies.py")"
>
> The "\" is being stripped from the config file when provided to qpidd and we get an error. Example "qpidd --config D:\qpid-cpp-trunk\config.conf" --> "cannot read configuration file D:qpid-cpp-trunkconfig.conf (You can run the cli_tests using ctest "ctest -R cli_tests -VV")
> Regards,Adel
> > From: adelboutros@live.com
> > To: users@qpid.apache.org
> > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > Date: Mon, 23 May 2016 15:51:28 +0200
> >
> > Yes sure, we can try to launch them on the trunk. I will let you know when this is done and how it turns out.
> > For the time being, we will stick with the already passing tests: 1/25 Test #1: qpid-client-test ................. Passed 1.01 sec 2/25 Test #2: quick_perftest ................... Passed 1.08 sec 3/25 Test #3: quick_topictest .................. Passed 3.94 sec 4/25 Test #4: quick_txtest ..................... Passed 1.01 sec 5/25 Test #5: quick_txtest2 .................... Passed 0.99 sec 6/25 Test #6: msg_group_tests .................. Passed 23.73 sec 7/25 Test #7: run_header_test .................. Passed 3.20 sec 8/25 Test #8: python_tests .....................***Failed 685.70 sec 9/25 Test #9: interop_tests ....................***Failed 0.82 sec10/25 Test #10: ha_tests ......................... Passed 1.56 sec11/25 Test #11: qpidd_qmfv2_tests ................***Failed 1.16 sec12/25 Test #12: interlink_tests ..................***Failed 0.87 sec13/25 Test #13: idle_timeout_tests ...............***Failed 1.13 sec14/25 Test #14: swig_python_tests ................***Failed 0.82 sec15/25 Test #15: ipv6_test ........................***Failed 0.78 sec16/25 Test #16: federation_tests .................***Failed 123.01 sec17/25 Test #17: federation_sys_tests .............***Failed 2.49 sec18/25 Test #18: queue_flow_limit_tests ........... Passed 1.37 sec19/25 Test #19: acl_tests ........................***Failed 20.30 sec20/25 Test #20: cli_tests ........................***Failed 0.37 sec21/25 Test #21: dynamic_log_level_test ...........***Failed 0.33 sec22/25 Test #22: dynamic_log_hires_timestamp ......***Failed 0.31 sec23/25 Test #23: store_tests ......................***Failed 153.19 sec24/25 Test #24: store_tests_clfs .................***Failed 153.92 sec25/25 Test #25: queue_redirect ...................***Failed 0.37 sec
> > PS: The ha_tests have a missing dependency but is marked as passed.
> > Regards,Adel
> >
> > > Date: Mon, 23 May 2016 05:52:38 -0700
> > > Subject: Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > > From: justin.ross@gmail.com
> > > To: users@qpid.apache.org
> > >
> > > On Mon, May 23, 2016 at 4:12 AM, <ad...@live.com> wrote:
> > >
> > > > 1) A missing powershell script(run_queue_redirect.ps1) forces a test
> > > > (queue_redirect) not to start
> > > >
> > >
> > > Given that it's not really in working shape, I would disable this test.
> > > Otherwise, you'll need to write the missing script. Even if you do write
> > > the missing script, there's no guarantee the test will work as expected,
> > > just because it wasn't ported to windows before and hasn't historically
> > > been under test.
> > >
> > >
> > > > 2) Python scripts can be executed on Linux without adding "python" prior
> > > > to the script name because it is detected from the first line in the script
> > > > (#!/usr/bin/env python). This doesn't work on Windows unless "py" extension
> > > > files are associated with python. To do this, all python scripts must end
> > > > with .py which is not the case for a lot of the scripts such as the qpidd
> > > > management tools (qpid-python-test, qpid-config, ...)
> > > >
> > >
> > > The tests wrt Windows have long been a problem. I started working on
> > > improving them a couple months ago. One of the things I did was add batch
> > > files for all the command line tools so that the test scripts could more
> > > easily use them.
> > >
> > > https://github.com/apache/qpid/blob/trunk/qpid/cpp/management/python/bin/qpid-config.bat
> > >
> > > That work is on trunk right now, set for release in Qpid C++ 1.35.0.
> > > That's coming in a month or so.
> > >
> > >
> > > > So we wanted to know if you could help us fix the above issues?
> > > >
> > > > We are currently debugging other issues as well and wanted to ask you to
> > > > confirm that some of the tests actually requires the management tools
> > > > installed as a pre-requisite?
> > > >
> > >
> > > That's right. Many of the tests require the management tools. As of
> > > 1.35.0, those tools are part of the C++ source tree.
> > >
> > > Care to try running the trunk tests? The changes there will address some
> > > of your problems, but there are definitely still known problems. I'd love
> > > to get your help to improve our tests in the next release.
> > >
> > > Justin
> >
>
RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Adel Boutros <ad...@live.com>.
Hello Justin,
I took the code from the trunk and started compiling and testing. I already have 2 issues to signal:There is a script launched "check_dependencies.py" in ctest directly. It is defined in CTestCustom.cmake. The issue is that if on my machine ".py" programs are configured to open in notepad, then the tests will fail. I propose to add the keyword"python" before the name of the script and set the correct python in the PATH environment variable. This way I can explicitly define which python version I want to use. So the line to change becomes "set(CTEST_CUSTOM_PRE_TEST "python ${CMAKE_BINARY_DIR}/src/tests/check_dependencies.py")"
The "\" is being stripped from the config file when provided to qpidd and we get an error. Example "qpidd --config D:\qpid-cpp-trunk\config.conf" --> "cannot read configuration file D:qpid-cpp-trunkconfig.conf (You can run the cli_tests using ctest "ctest -R cli_tests -VV")
Regards,Adel
> From: adelboutros@live.com
> To: users@qpid.apache.org
> Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> Date: Mon, 23 May 2016 15:51:28 +0200
>
> Yes sure, we can try to launch them on the trunk. I will let you know when this is done and how it turns out.
> For the time being, we will stick with the already passing tests: 1/25 Test #1: qpid-client-test ................. Passed 1.01 sec 2/25 Test #2: quick_perftest ................... Passed 1.08 sec 3/25 Test #3: quick_topictest .................. Passed 3.94 sec 4/25 Test #4: quick_txtest ..................... Passed 1.01 sec 5/25 Test #5: quick_txtest2 .................... Passed 0.99 sec 6/25 Test #6: msg_group_tests .................. Passed 23.73 sec 7/25 Test #7: run_header_test .................. Passed 3.20 sec 8/25 Test #8: python_tests .....................***Failed 685.70 sec 9/25 Test #9: interop_tests ....................***Failed 0.82 sec10/25 Test #10: ha_tests ......................... Passed 1.56 sec11/25 Test #11: qpidd_qmfv2_tests ................***Failed 1.16 sec12/25 Test #12: interlink_tests ..................***Failed 0.87 sec13/25 Test #13: idle_timeout_tests ...............***Failed 1.13 sec14/25 Test #14: swig_python_tests ................***Failed 0.82 sec15/25 Test #15: ipv6_test ........................***Failed 0.78 sec16/25 Test #16: federation_tests .................***Failed 123.01 sec17/25 Test #17: federation_sys_tests .............***Failed 2.49 sec18/25 Test #18: queue_flow_limit_tests ........... Passed 1.37 sec19/25 Test #19: acl_tests ........................***Failed 20.30 sec20/25 Test #20: cli_tests ........................***Failed 0.37 sec21/25 Test #21: dynamic_log_level_test ...........***Failed 0.33 sec22/25 Test #22: dynamic_log_hires_timestamp ......***Failed 0.31 sec23/25 Test #23: store_tests ......................***Failed 153.19 sec24/25 Test #24: store_tests_clfs .................***Failed 153.92 sec25/25 Test #25: queue_redirect ...................***Failed 0.37 sec
> PS: The ha_tests have a missing dependency but is marked as passed.
> Regards,Adel
>
> > Date: Mon, 23 May 2016 05:52:38 -0700
> > Subject: Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > From: justin.ross@gmail.com
> > To: users@qpid.apache.org
> >
> > On Mon, May 23, 2016 at 4:12 AM, <ad...@live.com> wrote:
> >
> > > 1) A missing powershell script(run_queue_redirect.ps1) forces a test
> > > (queue_redirect) not to start
> > >
> >
> > Given that it's not really in working shape, I would disable this test.
> > Otherwise, you'll need to write the missing script. Even if you do write
> > the missing script, there's no guarantee the test will work as expected,
> > just because it wasn't ported to windows before and hasn't historically
> > been under test.
> >
> >
> > > 2) Python scripts can be executed on Linux without adding "python" prior
> > > to the script name because it is detected from the first line in the script
> > > (#!/usr/bin/env python). This doesn't work on Windows unless "py" extension
> > > files are associated with python. To do this, all python scripts must end
> > > with .py which is not the case for a lot of the scripts such as the qpidd
> > > management tools (qpid-python-test, qpid-config, ...)
> > >
> >
> > The tests wrt Windows have long been a problem. I started working on
> > improving them a couple months ago. One of the things I did was add batch
> > files for all the command line tools so that the test scripts could more
> > easily use them.
> >
> > https://github.com/apache/qpid/blob/trunk/qpid/cpp/management/python/bin/qpid-config.bat
> >
> > That work is on trunk right now, set for release in Qpid C++ 1.35.0.
> > That's coming in a month or so.
> >
> >
> > > So we wanted to know if you could help us fix the above issues?
> > >
> > > We are currently debugging other issues as well and wanted to ask you to
> > > confirm that some of the tests actually requires the management tools
> > > installed as a pre-requisite?
> > >
> >
> > That's right. Many of the tests require the management tools. As of
> > 1.35.0, those tools are part of the C++ source tree.
> >
> > Care to try running the trunk tests? The changes there will address some
> > of your problems, but there are definitely still known problems. I'd love
> > to get your help to improve our tests in the next release.
> >
> > Justin
>
RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Adel Boutros <ad...@live.com>.
Yes sure, we can try to launch them on the trunk. I will let you know when this is done and how it turns out.
For the time being, we will stick with the already passing tests: 1/25 Test #1: qpid-client-test ................. Passed 1.01 sec 2/25 Test #2: quick_perftest ................... Passed 1.08 sec 3/25 Test #3: quick_topictest .................. Passed 3.94 sec 4/25 Test #4: quick_txtest ..................... Passed 1.01 sec 5/25 Test #5: quick_txtest2 .................... Passed 0.99 sec 6/25 Test #6: msg_group_tests .................. Passed 23.73 sec 7/25 Test #7: run_header_test .................. Passed 3.20 sec 8/25 Test #8: python_tests .....................***Failed 685.70 sec 9/25 Test #9: interop_tests ....................***Failed 0.82 sec10/25 Test #10: ha_tests ......................... Passed 1.56 sec11/25 Test #11: qpidd_qmfv2_tests ................***Failed 1.16 sec12/25 Test #12: interlink_tests ..................***Failed 0.87 sec13/25 Test #13: idle_timeout_tests ...............***Failed 1.13 sec14/25 Test #14: swig_python_tests ................***Failed 0.82 sec15/25 Test #15: ipv6_test ........................***Failed 0.78 sec16/25 Test #16: federation_tests .................***Failed 123.01 sec17/25 Test #17: federation_sys_tests .............***Failed 2.49 sec18/25 Test #18: queue_flow_limit_tests ........... Passed 1.37 sec19/25 Test #19: acl_tests ........................***Failed 20.30 sec20/25 Test #20: cli_tests ........................***Failed 0.37 sec21/25 Test #21: dynamic_log_level_test ...........***Failed 0.33 sec22/25 Test #22: dynamic_log_hires_timestamp ......***Failed 0.31 sec23/25 Test #23: store_tests ......................***Failed 153.19 sec24/25 Test #24: store_tests_clfs .................***Failed 153.92 sec25/25 Test #25: queue_redirect ...................***Failed 0.37 sec
PS: The ha_tests have a missing dependency but is marked as passed.
Regards,Adel
> Date: Mon, 23 May 2016 05:52:38 -0700
> Subject: Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> From: justin.ross@gmail.com
> To: users@qpid.apache.org
>
> On Mon, May 23, 2016 at 4:12 AM, <ad...@live.com> wrote:
>
> > 1) A missing powershell script(run_queue_redirect.ps1) forces a test
> > (queue_redirect) not to start
> >
>
> Given that it's not really in working shape, I would disable this test.
> Otherwise, you'll need to write the missing script. Even if you do write
> the missing script, there's no guarantee the test will work as expected,
> just because it wasn't ported to windows before and hasn't historically
> been under test.
>
>
> > 2) Python scripts can be executed on Linux without adding "python" prior
> > to the script name because it is detected from the first line in the script
> > (#!/usr/bin/env python). This doesn't work on Windows unless "py" extension
> > files are associated with python. To do this, all python scripts must end
> > with .py which is not the case for a lot of the scripts such as the qpidd
> > management tools (qpid-python-test, qpid-config, ...)
> >
>
> The tests wrt Windows have long been a problem. I started working on
> improving them a couple months ago. One of the things I did was add batch
> files for all the command line tools so that the test scripts could more
> easily use them.
>
> https://github.com/apache/qpid/blob/trunk/qpid/cpp/management/python/bin/qpid-config.bat
>
> That work is on trunk right now, set for release in Qpid C++ 1.35.0.
> That's coming in a month or so.
>
>
> > So we wanted to know if you could help us fix the above issues?
> >
> > We are currently debugging other issues as well and wanted to ask you to
> > confirm that some of the tests actually requires the management tools
> > installed as a pre-requisite?
> >
>
> That's right. Many of the tests require the management tools. As of
> 1.35.0, those tools are part of the C++ source tree.
>
> Care to try running the trunk tests? The changes there will address some
> of your problems, but there are definitely still known problems. I'd love
> to get your help to improve our tests in the next release.
>
> Justin
RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Adel Boutros <ad...@live.com>.
I am taking a look at the failures I have for all the tests. I have the same failures as you do plus the 2 below:
interlink_tests
In some of the tests, you use the option "--socket-fd" which is not recognized on Windows.
[Broker] critical Unexpected error: Error in command line options: unrecognised option '--socket-fd=1184'
This value is used here: src\qpid\broker\posix\SocketFDPlugin.cpp
I think there is a missing implementation for Windows regarding the SocketFDPlugin, no?
interop_testsMy PYTHONPATH was missing a directory build-directory\bindings\qpid\python\RelWithDebInfo. When I added it, Have the following failure and then the test hangs:
1: cpp/src/tests/exception_test.cpp(69): error in "DisconnectedPop": Bad exception: Timed out waiting for amessage[class qpid::Exception] expected: struct qpid::TransportFailure1: cpp/src/tests/exception_test.cpp(100): error in "DisconnectedPop": check pop.join() failed
I suspect it has to do with the fact I have disabled SSL and all of the interop_tests seem to require SSL
Regards,Adel
> From: adelboutros@live.com
> To: users@qpid.apache.org
> Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> Date: Wed, 1 Jun 2016 15:22:04 +0200
>
> Hello Justin,
> I took a look at the appveyor link you sent and there 2 issues which I wanted to raise:In your cmake, Proton is not found (Some of the tests are skipped or disabled)SWIG is not present (I believe it is also used in the tests)
> This is why you have only 12 total tests while I have 15 tests
> The following tests FAILED: 4 - federation_tests (Failed) 5 - flow_control_tests (Timeout) 8 - python_tests (Timeout) 13 - interlink_tests (Failed) 14 - interop_tests (Failed) 15 - windows_store_tests (Failed)
> Regards,Adel
> > Date: Tue, 31 May 2016 21:14:00 -0700
> > Subject: Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > From: justin.ross@gmail.com
> > To: users@qpid.apache.org
> >
> > https://svn.apache.org/viewvc?view=revision&revision=1746375
> >
> > I believe I've fixed the issues you've raised so far. Now on to new ones.
> >
> > In general, I won't have much time to work more on this in the near future,
> > but I think we are closer to seeing real test failures as opposed to
> > problems in the test scripting.
> >
> > Latest results:
> > https://ci.appveyor.com/project/ssorj/qpid-svn-reorg/build/hammerandtong.76
> >
> > I had my test timeout set relatively low. In other runs, the python_tests
> > were also failing, not timing out. I'm also now skipping the unit_tests
> > because of the SSL issue I haven't been able to resolve.
> >
> > The following tests FAILED:
> > 4 - federation_tests (Failed)
> > 5 - flow_control_tests (Timeout)
> > 8 - python_tests (Timeout)
> > 12 - windows_store_tests (Failed)
> > Errors while running CTest
> >
> > 4: run_federation_tests: Calling 'qpid-python-test --broker localhost:1760
> > --time -m headers_federation -Dremote-port=1762'
> > 4: headers_federation.HeadersFederationTests.test_dynamic_headers_unbind
> > ... fail
> > 4: Error during test: Traceback (most recent call last):
> > 4: File "C:\projects\qpid-svn-reorg\build\python\bin\\qpid-python-test",
> > line 340, in run
> > 4: phase()
> > 4: File
> > "C:\projects\qpid-svn-reorg\build\cpp\src\tests\headers_federation.py",
> > line 88, in test_dynamic_headers_unbind
> > 4: self.verify_cleanup()
> > 4: File
> > "C:\projects\qpid-svn-reorg\build\cpp\src\tests\headers_federation.py",
> > line 41, in verify_cleanup
> > 4: self.fail("Bridges and links didn't clean up")
> > 4: File "C:\Python27\lib\unittest\case.py", line 410, in fail
> > 4: raise self.failureException(msg)
> > 4: AssertionError: Bridges and links didn't clean up
> > 4: Totals: 1 tests, 0 passed, 0 skipped, 0 ignored, 1 failed
> >
> > 12: store.StoreTests.testDtxRecoverPrepared
> > ................................. fail
> > 12: Error during test: Traceback (most recent call last):
> > 12: File "C:\projects\qpid-svn-reorg\build\python\bin\\qpid-python-test",
> > line 340, in run
> > 12: phase()
> > 12: File "C:\projects\qpid-svn-reorg\build\cpp\src\tests\store.py", line
> > 195, in testDtxRecoverPrepared
> > 12: self.assert_(xid_matched)
> > 12: File "C:\Python27\lib\unittest\case.py", line 422, in assertTrue
> > 12: raise self.failureException(msg)
> > 12: AssertionError: False is not true
> >
> > On Tue, May 31, 2016 at 6:28 AM, Adel Boutros <ad...@live.com> wrote:
> >
> > > Hello Justin,
> > >
> > >
> > >
> > > When do
> > > you think you will have time to fix those issues?
> > >
> > >
> > >
> > > Regards,
> > >
> > > Adel
> > > > From: adelboutros@live.com
> > > > To: users@qpid.apache.org
> > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > > > Date: Fri, 27 May 2016 18:31:29 +0200
> > > >
> > > > In env.py.in, all libraries are ".so" extension which will not work on
> > > Windows as you will need ".dll" instead
> > > >
> > > > _export_module("HA_LIB", join(BUILD_DIR, "src",
> > > "ha.so"))_export_module("XML_LIB", join(BUILD_DIR, "src",
> > > "xml.so"))_export_module("AMQP_LIB", join(BUILD_DIR, "src",
> > > "amqp.so"))_export_module("TEST_STORE_LIB", join(BUILD_DIR, "src", "tests",
> > > "test_store.so"))_export_module("STORE_LIB", join(BUILD_DIR, "src",
> > > "linearstore.so"))
> > > > > From: adelboutros@live.com
> > > > > To: users@qpid.apache.org
> > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio
> > > 2013
> > > > > Date: Fri, 27 May 2016 17:49:46 +0200
> > > > >
> > > > > In qmf_tests, in brokertest.py, there is something wrong with the path
> > > because the script cannot find "qpidd" executable. If you add the ".exe"
> > > extension then it works.
> > > > > I noticed that all other tests use "common.py" for qpidd. So why is
> > > this test different?
> > > > > Fixing the path makes the test pass and it fixes the same error in
> > > other tests.
> > > > > Error: AssertionError: executable not found: qpiddFix: qpidd_exec =
> > > "qpidd.exe" (In brokertest.py)
> > > > > Regards,Adel
> > > > >
> > > > > > Date: Fri, 27 May 2016 07:59:34 -0700
> > > > > > Subject: Re: Qpid C++ 0.34 unit tests are failing with visual studio
> > > 2013
> > > > > > From: justin.ross@gmail.com
> > > > > > To: users@qpid.apache.org
> > > > > >
> > > > > > Yeah, that's a simple bug on my end. I'll get that fixed and report
> > > back.
> > > > > >
> > > > > > On Fri, May 27, 2016 at 7:52 AM, Adel Boutros <ad...@live.com>
> > > wrote:
> > > > > >
> > > > > > > Also, in env.ps1.in, there is a reference to "$builddir" but it
> > > never has
> > > > > > > value so the tests needing PYTHON_DIR will always fail.
> > > > > > > $PYTHON_DIR="$builddir\python" ---> is interpreted as "\python"
> > > > > > > I think there is a missing link between "$builddir" and some Cmake
> > > > > > > variable.
> > > > > > > > From: adelboutros@live.com
> > > > > > > > To: users@qpid.apache.org
> > > > > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual
> > > studio 2013
> > > > > > > > Date: Fri, 27 May 2016 16:31:44 +0200
> > > > > > > >
> > > > > > > > Hello Justin,
> > > > > > > > So I launched all the tests and I have 10 failing including the
> > > > > > > unit_tests (There is a disconnection error which I can also see in
> > > your
> > > > > > > appveyor).
> > > > > > > >
> > > > > > > > The following tests FAILED: 4 - federation_tests (Failed)
> > > 5 -
> > > > > > > flow_control_tests (Timeout) 6 - ha_tests (Failed) 9 -
> > > > > > > python_tests (Failed) 11 - qmf_tests (Failed) 14 -
> > > > > > > interlink_tests (Failed) 15 - interop_tests (Timeout) 16 -
> > > store_tests
> > > > > > > (Failed) 17 - store_tests_clfs (Failed)
> > > > > > > > For the store_tests, powershell scripts in current directory
> > > cannot be
> > > > > > > launched as they are not trusted, so you should add ".\" prior to
> > > the
> > > > > > > script name.
> > > > > > > > C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
> > > > > > > "run_store_tests.ps1" "MSSQL"The error message is helpful
> > > > > > > actually:run_store_tests.ps1 : The term 'run_store_tests.ps1' is
> > > not
> > > > > > > recognized as the name of a cmdlet, function... Suggestion
> > > [3,General]: The
> > > > > > > command run_store_tests.ps1 was not found, but does exist in the
> > > current
> > > > > > > location. Windows PowerShell does not load commands from the
> > > current
> > > > > > > location by default. If you trust this command, instead type
> > > > > > > ".\run_store_tests.ps1". See "get-help about_Command_Precedence"
> > > for more
> > > > > > > details.
> > > > > > > > I am still debugging the other tests.
> > > > > > > > Have you had a better luck than mine?
> > > > > > > > I can send you the test logs if you like.
> > > > > > > > PS: I am compiling with SASL/SSL disabled and valgrind disabled
> > > also
> > > > > > > completely.
> > > > > > > > Regards,Adel
> > > > > > > > > From: adelboutros@live.com
> > > > > > > > > To: users@qpid.apache.org
> > > > > > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual
> > > studio
> > > > > > > 2013
> > > > > > > > > Date: Fri, 27 May 2016 12:02:40 +0200
> > > > > > > > >
> > > > > > > > > Please ignore my last email. There was a problem with the PATH
> > > > > > > environment variable.
> > > > > > > > >
> > > > > > > > > > From: adelboutros@live.com
> > > > > > > > > > To: users@qpid.apache.org
> > > > > > > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with
> > > visual studio
> > > > > > > 2013
> > > > > > > > > > Date: Fri, 27 May 2016 11:40:58 +0200
> > > > > > > > > >
> > > > > > > > > > Hello Justin,
> > > > > > > > > > I updated to the head of the trunk and relaunched
> > > everything. I
> > > > > > > still have a problem with the qpid tools.I can see all the bat
> > > files, but
> > > > > > > the code still calls the original files for example:
> > > > > > > > > > 1: run_acl_tests: Calling 'qpid-python-test --broker
> > > localhost:63666
> > > > > > > --time -m acl -Dport-i=63668 -Dport-u=63710 -Dport-q=63712
> > > > > > >
> > > -Dpolicy-file=D:\qpid-cpp-trunk.git\qpid\qpid\cpp\build-dir-RelWithDebInfo\src\tests\policy.acl'1:
> > > > > > > 'qpid-python-test' is not recognized as an internal or external
> > > command,
> > > > > > > > > > All the .py files have not been updated to launch
> > > > > > > qpid-python-test.bat when on windows:Example:
> > > > > > > qpid/cpp/src/tests/run_interop_testscall("qpid-python-test -m
> > > interop_tests
> > > > > > > -DOUTDIR={0}", WORK_DIR)
> > > > > > > > > > Regards,Adel
> > > > > > > > > > > Date: Thu, 26 May 2016 15:02:59 -0700
> > > > > > > > > > > Subject: Re: Qpid C++ 0.34 unit tests are failing with
> > > visual
> > > > > > > studio 2013
> > > > > > > > > > > From: justin.ross@gmail.com
> > > > > > > > > > > To: users@qpid.apache.org
> > > > > > > > > > >
> > > > > > > > > > > An update. I think I've fixed the python and backslash
> > > problems.
> > > > > > > > > > >
> > > > > > > > > > > https://issues.apache.org/jira/browse/QPID-7281
> > > > > > > > > > >
> > > > > > > > > > > Here's what I get now in appveyor:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > >
> > > https://ci.appveyor.com/project/ssorj/qpid-svn-reorg/build/hammerandtong.71
> > > > > > > > > > >
> > > > > > > > > > > The unit_test failure is one I've had for a long time.
> > > I've not
> > > > > > > yet been
> > > > > > > > > > > able to convince either appveyor to use "localhost" for its
> > > > > > > hostname or
> > > > > > > > > > > unit_test to use "appveyor-vm" as its ssl cert name. So
> > > it times
> > > > > > > out.
> > > > > > > > > > >
> > > > > > > > > > > The other tests are running now, with some failures. Note
> > > that up
> > > > > > > to now
> > > > > > > > > > > I've been liberal in enabling the cross-platform tests
> > > that can
> > > > > > > > > > > hypothetically work in windows. There may be specific
> > > instances
> > > > > > > where I'm
> > > > > > > > > > > wrong, and we'll need to adjust the target platform for
> > > the test.
> > > > > > > > > > >
> > > > > > > > > > > On Thu, May 26, 2016 at 9:45 AM, Andrew Stitcher <
> > > > > > > astitcher@redhat.com>
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > On Thu, 2016-05-26 at 09:38 -0700, Justin Ross wrote:
> > > > > > > > > > > > > I tried this approach first. I wasn't able to make
> > > that
> > > > > > > > > > > > > configuration
> > > > > > > > > > > > > available in CTestCustom.cmake when I tried last.
> > > However, I
> > > > > > > don't
> > > > > > > > > > > > > think I
> > > > > > > > > > > > > tried repeating the find_package logic directly in the
> > > > > > > custom.cmake
> > > > > > > > > > > > > file,
> > > > > > > > > > > > > which I will do.
> > > > > > > > > > > >
> > > > > > > > > > > > CMake is hierarchical so the find_package() would need
> > > to be in
> > > > > > > a CMake
> > > > > > > > > > > > file above the relevant one (and perhaps in the sequence
> > > before
> > > > > > > the
> > > > > > > > > > > > add_directory(..) or include(...) that includes the file
> > > you
> > > > > > > want the
> > > > > > > > > > > > definition in - I'm not too clear about that point.
> > > > > > > > > > > >
> > > > > > > > > > > > Andrew
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > > > > > > To unsubscribe, e-mail:
> > > users-unsubscribe@qpid.apache.org
> > > > > > > > > > > > For additional commands, e-mail:
> > > users-help@qpid.apache.org
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > >
> > >
> > >
>
RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Adel Boutros <ad...@live.com>.
Hello Justin,
I took a look at the appveyor link you sent and there 2 issues which I wanted to raise:In your cmake, Proton is not found (Some of the tests are skipped or disabled)SWIG is not present (I believe it is also used in the tests)
This is why you have only 12 total tests while I have 15 tests
The following tests FAILED: 4 - federation_tests (Failed) 5 - flow_control_tests (Timeout) 8 - python_tests (Timeout) 13 - interlink_tests (Failed) 14 - interop_tests (Failed) 15 - windows_store_tests (Failed)
Regards,Adel
> Date: Tue, 31 May 2016 21:14:00 -0700
> Subject: Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> From: justin.ross@gmail.com
> To: users@qpid.apache.org
>
> https://svn.apache.org/viewvc?view=revision&revision=1746375
>
> I believe I've fixed the issues you've raised so far. Now on to new ones.
>
> In general, I won't have much time to work more on this in the near future,
> but I think we are closer to seeing real test failures as opposed to
> problems in the test scripting.
>
> Latest results:
> https://ci.appveyor.com/project/ssorj/qpid-svn-reorg/build/hammerandtong.76
>
> I had my test timeout set relatively low. In other runs, the python_tests
> were also failing, not timing out. I'm also now skipping the unit_tests
> because of the SSL issue I haven't been able to resolve.
>
> The following tests FAILED:
> 4 - federation_tests (Failed)
> 5 - flow_control_tests (Timeout)
> 8 - python_tests (Timeout)
> 12 - windows_store_tests (Failed)
> Errors while running CTest
>
> 4: run_federation_tests: Calling 'qpid-python-test --broker localhost:1760
> --time -m headers_federation -Dremote-port=1762'
> 4: headers_federation.HeadersFederationTests.test_dynamic_headers_unbind
> ... fail
> 4: Error during test: Traceback (most recent call last):
> 4: File "C:\projects\qpid-svn-reorg\build\python\bin\\qpid-python-test",
> line 340, in run
> 4: phase()
> 4: File
> "C:\projects\qpid-svn-reorg\build\cpp\src\tests\headers_federation.py",
> line 88, in test_dynamic_headers_unbind
> 4: self.verify_cleanup()
> 4: File
> "C:\projects\qpid-svn-reorg\build\cpp\src\tests\headers_federation.py",
> line 41, in verify_cleanup
> 4: self.fail("Bridges and links didn't clean up")
> 4: File "C:\Python27\lib\unittest\case.py", line 410, in fail
> 4: raise self.failureException(msg)
> 4: AssertionError: Bridges and links didn't clean up
> 4: Totals: 1 tests, 0 passed, 0 skipped, 0 ignored, 1 failed
>
> 12: store.StoreTests.testDtxRecoverPrepared
> ................................. fail
> 12: Error during test: Traceback (most recent call last):
> 12: File "C:\projects\qpid-svn-reorg\build\python\bin\\qpid-python-test",
> line 340, in run
> 12: phase()
> 12: File "C:\projects\qpid-svn-reorg\build\cpp\src\tests\store.py", line
> 195, in testDtxRecoverPrepared
> 12: self.assert_(xid_matched)
> 12: File "C:\Python27\lib\unittest\case.py", line 422, in assertTrue
> 12: raise self.failureException(msg)
> 12: AssertionError: False is not true
>
> On Tue, May 31, 2016 at 6:28 AM, Adel Boutros <ad...@live.com> wrote:
>
> > Hello Justin,
> >
> >
> >
> > When do
> > you think you will have time to fix those issues?
> >
> >
> >
> > Regards,
> >
> > Adel
> > > From: adelboutros@live.com
> > > To: users@qpid.apache.org
> > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > > Date: Fri, 27 May 2016 18:31:29 +0200
> > >
> > > In env.py.in, all libraries are ".so" extension which will not work on
> > Windows as you will need ".dll" instead
> > >
> > > _export_module("HA_LIB", join(BUILD_DIR, "src",
> > "ha.so"))_export_module("XML_LIB", join(BUILD_DIR, "src",
> > "xml.so"))_export_module("AMQP_LIB", join(BUILD_DIR, "src",
> > "amqp.so"))_export_module("TEST_STORE_LIB", join(BUILD_DIR, "src", "tests",
> > "test_store.so"))_export_module("STORE_LIB", join(BUILD_DIR, "src",
> > "linearstore.so"))
> > > > From: adelboutros@live.com
> > > > To: users@qpid.apache.org
> > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio
> > 2013
> > > > Date: Fri, 27 May 2016 17:49:46 +0200
> > > >
> > > > In qmf_tests, in brokertest.py, there is something wrong with the path
> > because the script cannot find "qpidd" executable. If you add the ".exe"
> > extension then it works.
> > > > I noticed that all other tests use "common.py" for qpidd. So why is
> > this test different?
> > > > Fixing the path makes the test pass and it fixes the same error in
> > other tests.
> > > > Error: AssertionError: executable not found: qpiddFix: qpidd_exec =
> > "qpidd.exe" (In brokertest.py)
> > > > Regards,Adel
> > > >
> > > > > Date: Fri, 27 May 2016 07:59:34 -0700
> > > > > Subject: Re: Qpid C++ 0.34 unit tests are failing with visual studio
> > 2013
> > > > > From: justin.ross@gmail.com
> > > > > To: users@qpid.apache.org
> > > > >
> > > > > Yeah, that's a simple bug on my end. I'll get that fixed and report
> > back.
> > > > >
> > > > > On Fri, May 27, 2016 at 7:52 AM, Adel Boutros <ad...@live.com>
> > wrote:
> > > > >
> > > > > > Also, in env.ps1.in, there is a reference to "$builddir" but it
> > never has
> > > > > > value so the tests needing PYTHON_DIR will always fail.
> > > > > > $PYTHON_DIR="$builddir\python" ---> is interpreted as "\python"
> > > > > > I think there is a missing link between "$builddir" and some Cmake
> > > > > > variable.
> > > > > > > From: adelboutros@live.com
> > > > > > > To: users@qpid.apache.org
> > > > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual
> > studio 2013
> > > > > > > Date: Fri, 27 May 2016 16:31:44 +0200
> > > > > > >
> > > > > > > Hello Justin,
> > > > > > > So I launched all the tests and I have 10 failing including the
> > > > > > unit_tests (There is a disconnection error which I can also see in
> > your
> > > > > > appveyor).
> > > > > > >
> > > > > > > The following tests FAILED: 4 - federation_tests (Failed)
> > 5 -
> > > > > > flow_control_tests (Timeout) 6 - ha_tests (Failed) 9 -
> > > > > > python_tests (Failed) 11 - qmf_tests (Failed) 14 -
> > > > > > interlink_tests (Failed) 15 - interop_tests (Timeout) 16 -
> > store_tests
> > > > > > (Failed) 17 - store_tests_clfs (Failed)
> > > > > > > For the store_tests, powershell scripts in current directory
> > cannot be
> > > > > > launched as they are not trusted, so you should add ".\" prior to
> > the
> > > > > > script name.
> > > > > > > C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
> > > > > > "run_store_tests.ps1" "MSSQL"The error message is helpful
> > > > > > actually:run_store_tests.ps1 : The term 'run_store_tests.ps1' is
> > not
> > > > > > recognized as the name of a cmdlet, function... Suggestion
> > [3,General]: The
> > > > > > command run_store_tests.ps1 was not found, but does exist in the
> > current
> > > > > > location. Windows PowerShell does not load commands from the
> > current
> > > > > > location by default. If you trust this command, instead type
> > > > > > ".\run_store_tests.ps1". See "get-help about_Command_Precedence"
> > for more
> > > > > > details.
> > > > > > > I am still debugging the other tests.
> > > > > > > Have you had a better luck than mine?
> > > > > > > I can send you the test logs if you like.
> > > > > > > PS: I am compiling with SASL/SSL disabled and valgrind disabled
> > also
> > > > > > completely.
> > > > > > > Regards,Adel
> > > > > > > > From: adelboutros@live.com
> > > > > > > > To: users@qpid.apache.org
> > > > > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual
> > studio
> > > > > > 2013
> > > > > > > > Date: Fri, 27 May 2016 12:02:40 +0200
> > > > > > > >
> > > > > > > > Please ignore my last email. There was a problem with the PATH
> > > > > > environment variable.
> > > > > > > >
> > > > > > > > > From: adelboutros@live.com
> > > > > > > > > To: users@qpid.apache.org
> > > > > > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with
> > visual studio
> > > > > > 2013
> > > > > > > > > Date: Fri, 27 May 2016 11:40:58 +0200
> > > > > > > > >
> > > > > > > > > Hello Justin,
> > > > > > > > > I updated to the head of the trunk and relaunched
> > everything. I
> > > > > > still have a problem with the qpid tools.I can see all the bat
> > files, but
> > > > > > the code still calls the original files for example:
> > > > > > > > > 1: run_acl_tests: Calling 'qpid-python-test --broker
> > localhost:63666
> > > > > > --time -m acl -Dport-i=63668 -Dport-u=63710 -Dport-q=63712
> > > > > >
> > -Dpolicy-file=D:\qpid-cpp-trunk.git\qpid\qpid\cpp\build-dir-RelWithDebInfo\src\tests\policy.acl'1:
> > > > > > 'qpid-python-test' is not recognized as an internal or external
> > command,
> > > > > > > > > All the .py files have not been updated to launch
> > > > > > qpid-python-test.bat when on windows:Example:
> > > > > > qpid/cpp/src/tests/run_interop_testscall("qpid-python-test -m
> > interop_tests
> > > > > > -DOUTDIR={0}", WORK_DIR)
> > > > > > > > > Regards,Adel
> > > > > > > > > > Date: Thu, 26 May 2016 15:02:59 -0700
> > > > > > > > > > Subject: Re: Qpid C++ 0.34 unit tests are failing with
> > visual
> > > > > > studio 2013
> > > > > > > > > > From: justin.ross@gmail.com
> > > > > > > > > > To: users@qpid.apache.org
> > > > > > > > > >
> > > > > > > > > > An update. I think I've fixed the python and backslash
> > problems.
> > > > > > > > > >
> > > > > > > > > > https://issues.apache.org/jira/browse/QPID-7281
> > > > > > > > > >
> > > > > > > > > > Here's what I get now in appveyor:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > >
> > https://ci.appveyor.com/project/ssorj/qpid-svn-reorg/build/hammerandtong.71
> > > > > > > > > >
> > > > > > > > > > The unit_test failure is one I've had for a long time.
> > I've not
> > > > > > yet been
> > > > > > > > > > able to convince either appveyor to use "localhost" for its
> > > > > > hostname or
> > > > > > > > > > unit_test to use "appveyor-vm" as its ssl cert name. So
> > it times
> > > > > > out.
> > > > > > > > > >
> > > > > > > > > > The other tests are running now, with some failures. Note
> > that up
> > > > > > to now
> > > > > > > > > > I've been liberal in enabling the cross-platform tests
> > that can
> > > > > > > > > > hypothetically work in windows. There may be specific
> > instances
> > > > > > where I'm
> > > > > > > > > > wrong, and we'll need to adjust the target platform for
> > the test.
> > > > > > > > > >
> > > > > > > > > > On Thu, May 26, 2016 at 9:45 AM, Andrew Stitcher <
> > > > > > astitcher@redhat.com>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > On Thu, 2016-05-26 at 09:38 -0700, Justin Ross wrote:
> > > > > > > > > > > > I tried this approach first. I wasn't able to make
> > that
> > > > > > > > > > > > configuration
> > > > > > > > > > > > available in CTestCustom.cmake when I tried last.
> > However, I
> > > > > > don't
> > > > > > > > > > > > think I
> > > > > > > > > > > > tried repeating the find_package logic directly in the
> > > > > > custom.cmake
> > > > > > > > > > > > file,
> > > > > > > > > > > > which I will do.
> > > > > > > > > > >
> > > > > > > > > > > CMake is hierarchical so the find_package() would need
> > to be in
> > > > > > a CMake
> > > > > > > > > > > file above the relevant one (and perhaps in the sequence
> > before
> > > > > > the
> > > > > > > > > > > add_directory(..) or include(...) that includes the file
> > you
> > > > > > want the
> > > > > > > > > > > definition in - I'm not too clear about that point.
> > > > > > > > > > >
> > > > > > > > > > > Andrew
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > > > > > > To unsubscribe, e-mail:
> > users-unsubscribe@qpid.apache.org
> > > > > > > > > > > For additional commands, e-mail:
> > users-help@qpid.apache.org
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > >
> > >
> >
> >
Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Justin Ross <ju...@gmail.com>.
https://svn.apache.org/viewvc?view=revision&revision=1746375
I believe I've fixed the issues you've raised so far. Now on to new ones.
In general, I won't have much time to work more on this in the near future,
but I think we are closer to seeing real test failures as opposed to
problems in the test scripting.
Latest results:
https://ci.appveyor.com/project/ssorj/qpid-svn-reorg/build/hammerandtong.76
I had my test timeout set relatively low. In other runs, the python_tests
were also failing, not timing out. I'm also now skipping the unit_tests
because of the SSL issue I haven't been able to resolve.
The following tests FAILED:
4 - federation_tests (Failed)
5 - flow_control_tests (Timeout)
8 - python_tests (Timeout)
12 - windows_store_tests (Failed)
Errors while running CTest
4: run_federation_tests: Calling 'qpid-python-test --broker localhost:1760
--time -m headers_federation -Dremote-port=1762'
4: headers_federation.HeadersFederationTests.test_dynamic_headers_unbind
... fail
4: Error during test: Traceback (most recent call last):
4: File "C:\projects\qpid-svn-reorg\build\python\bin\\qpid-python-test",
line 340, in run
4: phase()
4: File
"C:\projects\qpid-svn-reorg\build\cpp\src\tests\headers_federation.py",
line 88, in test_dynamic_headers_unbind
4: self.verify_cleanup()
4: File
"C:\projects\qpid-svn-reorg\build\cpp\src\tests\headers_federation.py",
line 41, in verify_cleanup
4: self.fail("Bridges and links didn't clean up")
4: File "C:\Python27\lib\unittest\case.py", line 410, in fail
4: raise self.failureException(msg)
4: AssertionError: Bridges and links didn't clean up
4: Totals: 1 tests, 0 passed, 0 skipped, 0 ignored, 1 failed
12: store.StoreTests.testDtxRecoverPrepared
................................. fail
12: Error during test: Traceback (most recent call last):
12: File "C:\projects\qpid-svn-reorg\build\python\bin\\qpid-python-test",
line 340, in run
12: phase()
12: File "C:\projects\qpid-svn-reorg\build\cpp\src\tests\store.py", line
195, in testDtxRecoverPrepared
12: self.assert_(xid_matched)
12: File "C:\Python27\lib\unittest\case.py", line 422, in assertTrue
12: raise self.failureException(msg)
12: AssertionError: False is not true
On Tue, May 31, 2016 at 6:28 AM, Adel Boutros <ad...@live.com> wrote:
> Hello Justin,
>
>
>
> When do
> you think you will have time to fix those issues?
>
>
>
> Regards,
>
> Adel
> > From: adelboutros@live.com
> > To: users@qpid.apache.org
> > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > Date: Fri, 27 May 2016 18:31:29 +0200
> >
> > In env.py.in, all libraries are ".so" extension which will not work on
> Windows as you will need ".dll" instead
> >
> > _export_module("HA_LIB", join(BUILD_DIR, "src",
> "ha.so"))_export_module("XML_LIB", join(BUILD_DIR, "src",
> "xml.so"))_export_module("AMQP_LIB", join(BUILD_DIR, "src",
> "amqp.so"))_export_module("TEST_STORE_LIB", join(BUILD_DIR, "src", "tests",
> "test_store.so"))_export_module("STORE_LIB", join(BUILD_DIR, "src",
> "linearstore.so"))
> > > From: adelboutros@live.com
> > > To: users@qpid.apache.org
> > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio
> 2013
> > > Date: Fri, 27 May 2016 17:49:46 +0200
> > >
> > > In qmf_tests, in brokertest.py, there is something wrong with the path
> because the script cannot find "qpidd" executable. If you add the ".exe"
> extension then it works.
> > > I noticed that all other tests use "common.py" for qpidd. So why is
> this test different?
> > > Fixing the path makes the test pass and it fixes the same error in
> other tests.
> > > Error: AssertionError: executable not found: qpiddFix: qpidd_exec =
> "qpidd.exe" (In brokertest.py)
> > > Regards,Adel
> > >
> > > > Date: Fri, 27 May 2016 07:59:34 -0700
> > > > Subject: Re: Qpid C++ 0.34 unit tests are failing with visual studio
> 2013
> > > > From: justin.ross@gmail.com
> > > > To: users@qpid.apache.org
> > > >
> > > > Yeah, that's a simple bug on my end. I'll get that fixed and report
> back.
> > > >
> > > > On Fri, May 27, 2016 at 7:52 AM, Adel Boutros <ad...@live.com>
> wrote:
> > > >
> > > > > Also, in env.ps1.in, there is a reference to "$builddir" but it
> never has
> > > > > value so the tests needing PYTHON_DIR will always fail.
> > > > > $PYTHON_DIR="$builddir\python" ---> is interpreted as "\python"
> > > > > I think there is a missing link between "$builddir" and some Cmake
> > > > > variable.
> > > > > > From: adelboutros@live.com
> > > > > > To: users@qpid.apache.org
> > > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual
> studio 2013
> > > > > > Date: Fri, 27 May 2016 16:31:44 +0200
> > > > > >
> > > > > > Hello Justin,
> > > > > > So I launched all the tests and I have 10 failing including the
> > > > > unit_tests (There is a disconnection error which I can also see in
> your
> > > > > appveyor).
> > > > > >
> > > > > > The following tests FAILED: 4 - federation_tests (Failed)
> 5 -
> > > > > flow_control_tests (Timeout) 6 - ha_tests (Failed) 9 -
> > > > > python_tests (Failed) 11 - qmf_tests (Failed) 14 -
> > > > > interlink_tests (Failed) 15 - interop_tests (Timeout) 16 -
> store_tests
> > > > > (Failed) 17 - store_tests_clfs (Failed)
> > > > > > For the store_tests, powershell scripts in current directory
> cannot be
> > > > > launched as they are not trusted, so you should add ".\" prior to
> the
> > > > > script name.
> > > > > > C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
> > > > > "run_store_tests.ps1" "MSSQL"The error message is helpful
> > > > > actually:run_store_tests.ps1 : The term 'run_store_tests.ps1' is
> not
> > > > > recognized as the name of a cmdlet, function... Suggestion
> [3,General]: The
> > > > > command run_store_tests.ps1 was not found, but does exist in the
> current
> > > > > location. Windows PowerShell does not load commands from the
> current
> > > > > location by default. If you trust this command, instead type
> > > > > ".\run_store_tests.ps1". See "get-help about_Command_Precedence"
> for more
> > > > > details.
> > > > > > I am still debugging the other tests.
> > > > > > Have you had a better luck than mine?
> > > > > > I can send you the test logs if you like.
> > > > > > PS: I am compiling with SASL/SSL disabled and valgrind disabled
> also
> > > > > completely.
> > > > > > Regards,Adel
> > > > > > > From: adelboutros@live.com
> > > > > > > To: users@qpid.apache.org
> > > > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual
> studio
> > > > > 2013
> > > > > > > Date: Fri, 27 May 2016 12:02:40 +0200
> > > > > > >
> > > > > > > Please ignore my last email. There was a problem with the PATH
> > > > > environment variable.
> > > > > > >
> > > > > > > > From: adelboutros@live.com
> > > > > > > > To: users@qpid.apache.org
> > > > > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with
> visual studio
> > > > > 2013
> > > > > > > > Date: Fri, 27 May 2016 11:40:58 +0200
> > > > > > > >
> > > > > > > > Hello Justin,
> > > > > > > > I updated to the head of the trunk and relaunched
> everything. I
> > > > > still have a problem with the qpid tools.I can see all the bat
> files, but
> > > > > the code still calls the original files for example:
> > > > > > > > 1: run_acl_tests: Calling 'qpid-python-test --broker
> localhost:63666
> > > > > --time -m acl -Dport-i=63668 -Dport-u=63710 -Dport-q=63712
> > > > >
> -Dpolicy-file=D:\qpid-cpp-trunk.git\qpid\qpid\cpp\build-dir-RelWithDebInfo\src\tests\policy.acl'1:
> > > > > 'qpid-python-test' is not recognized as an internal or external
> command,
> > > > > > > > All the .py files have not been updated to launch
> > > > > qpid-python-test.bat when on windows:Example:
> > > > > qpid/cpp/src/tests/run_interop_testscall("qpid-python-test -m
> interop_tests
> > > > > -DOUTDIR={0}", WORK_DIR)
> > > > > > > > Regards,Adel
> > > > > > > > > Date: Thu, 26 May 2016 15:02:59 -0700
> > > > > > > > > Subject: Re: Qpid C++ 0.34 unit tests are failing with
> visual
> > > > > studio 2013
> > > > > > > > > From: justin.ross@gmail.com
> > > > > > > > > To: users@qpid.apache.org
> > > > > > > > >
> > > > > > > > > An update. I think I've fixed the python and backslash
> problems.
> > > > > > > > >
> > > > > > > > > https://issues.apache.org/jira/browse/QPID-7281
> > > > > > > > >
> > > > > > > > > Here's what I get now in appveyor:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > >
> https://ci.appveyor.com/project/ssorj/qpid-svn-reorg/build/hammerandtong.71
> > > > > > > > >
> > > > > > > > > The unit_test failure is one I've had for a long time.
> I've not
> > > > > yet been
> > > > > > > > > able to convince either appveyor to use "localhost" for its
> > > > > hostname or
> > > > > > > > > unit_test to use "appveyor-vm" as its ssl cert name. So
> it times
> > > > > out.
> > > > > > > > >
> > > > > > > > > The other tests are running now, with some failures. Note
> that up
> > > > > to now
> > > > > > > > > I've been liberal in enabling the cross-platform tests
> that can
> > > > > > > > > hypothetically work in windows. There may be specific
> instances
> > > > > where I'm
> > > > > > > > > wrong, and we'll need to adjust the target platform for
> the test.
> > > > > > > > >
> > > > > > > > > On Thu, May 26, 2016 at 9:45 AM, Andrew Stitcher <
> > > > > astitcher@redhat.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > On Thu, 2016-05-26 at 09:38 -0700, Justin Ross wrote:
> > > > > > > > > > > I tried this approach first. I wasn't able to make
> that
> > > > > > > > > > > configuration
> > > > > > > > > > > available in CTestCustom.cmake when I tried last.
> However, I
> > > > > don't
> > > > > > > > > > > think I
> > > > > > > > > > > tried repeating the find_package logic directly in the
> > > > > custom.cmake
> > > > > > > > > > > file,
> > > > > > > > > > > which I will do.
> > > > > > > > > >
> > > > > > > > > > CMake is hierarchical so the find_package() would need
> to be in
> > > > > a CMake
> > > > > > > > > > file above the relevant one (and perhaps in the sequence
> before
> > > > > the
> > > > > > > > > > add_directory(..) or include(...) that includes the file
> you
> > > > > want the
> > > > > > > > > > definition in - I'm not too clear about that point.
> > > > > > > > > >
> > > > > > > > > > Andrew
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > > > > > > To unsubscribe, e-mail:
> users-unsubscribe@qpid.apache.org
> > > > > > > > > > For additional commands, e-mail:
> users-help@qpid.apache.org
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > >
> >
>
>
RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Adel Boutros <ad...@live.com>.
Hello Justin,
When do
you think you will have time to fix those issues?
Regards,
Adel
> From: adelboutros@live.com
> To: users@qpid.apache.org
> Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> Date: Fri, 27 May 2016 18:31:29 +0200
>
> In env.py.in, all libraries are ".so" extension which will not work on Windows as you will need ".dll" instead
>
> _export_module("HA_LIB", join(BUILD_DIR, "src", "ha.so"))_export_module("XML_LIB", join(BUILD_DIR, "src", "xml.so"))_export_module("AMQP_LIB", join(BUILD_DIR, "src", "amqp.so"))_export_module("TEST_STORE_LIB", join(BUILD_DIR, "src", "tests", "test_store.so"))_export_module("STORE_LIB", join(BUILD_DIR, "src", "linearstore.so"))
> > From: adelboutros@live.com
> > To: users@qpid.apache.org
> > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > Date: Fri, 27 May 2016 17:49:46 +0200
> >
> > In qmf_tests, in brokertest.py, there is something wrong with the path because the script cannot find "qpidd" executable. If you add the ".exe" extension then it works.
> > I noticed that all other tests use "common.py" for qpidd. So why is this test different?
> > Fixing the path makes the test pass and it fixes the same error in other tests.
> > Error: AssertionError: executable not found: qpiddFix: qpidd_exec = "qpidd.exe" (In brokertest.py)
> > Regards,Adel
> >
> > > Date: Fri, 27 May 2016 07:59:34 -0700
> > > Subject: Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > > From: justin.ross@gmail.com
> > > To: users@qpid.apache.org
> > >
> > > Yeah, that's a simple bug on my end. I'll get that fixed and report back.
> > >
> > > On Fri, May 27, 2016 at 7:52 AM, Adel Boutros <ad...@live.com> wrote:
> > >
> > > > Also, in env.ps1.in, there is a reference to "$builddir" but it never has
> > > > value so the tests needing PYTHON_DIR will always fail.
> > > > $PYTHON_DIR="$builddir\python" ---> is interpreted as "\python"
> > > > I think there is a missing link between "$builddir" and some Cmake
> > > > variable.
> > > > > From: adelboutros@live.com
> > > > > To: users@qpid.apache.org
> > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > > > > Date: Fri, 27 May 2016 16:31:44 +0200
> > > > >
> > > > > Hello Justin,
> > > > > So I launched all the tests and I have 10 failing including the
> > > > unit_tests (There is a disconnection error which I can also see in your
> > > > appveyor).
> > > > >
> > > > > The following tests FAILED: 4 - federation_tests (Failed) 5 -
> > > > flow_control_tests (Timeout) 6 - ha_tests (Failed) 9 -
> > > > python_tests (Failed) 11 - qmf_tests (Failed) 14 -
> > > > interlink_tests (Failed) 15 - interop_tests (Timeout) 16 - store_tests
> > > > (Failed) 17 - store_tests_clfs (Failed)
> > > > > For the store_tests, powershell scripts in current directory cannot be
> > > > launched as they are not trusted, so you should add ".\" prior to the
> > > > script name.
> > > > > C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
> > > > "run_store_tests.ps1" "MSSQL"The error message is helpful
> > > > actually:run_store_tests.ps1 : The term 'run_store_tests.ps1' is not
> > > > recognized as the name of a cmdlet, function... Suggestion [3,General]: The
> > > > command run_store_tests.ps1 was not found, but does exist in the current
> > > > location. Windows PowerShell does not load commands from the current
> > > > location by default. If you trust this command, instead type
> > > > ".\run_store_tests.ps1". See "get-help about_Command_Precedence" for more
> > > > details.
> > > > > I am still debugging the other tests.
> > > > > Have you had a better luck than mine?
> > > > > I can send you the test logs if you like.
> > > > > PS: I am compiling with SASL/SSL disabled and valgrind disabled also
> > > > completely.
> > > > > Regards,Adel
> > > > > > From: adelboutros@live.com
> > > > > > To: users@qpid.apache.org
> > > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio
> > > > 2013
> > > > > > Date: Fri, 27 May 2016 12:02:40 +0200
> > > > > >
> > > > > > Please ignore my last email. There was a problem with the PATH
> > > > environment variable.
> > > > > >
> > > > > > > From: adelboutros@live.com
> > > > > > > To: users@qpid.apache.org
> > > > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio
> > > > 2013
> > > > > > > Date: Fri, 27 May 2016 11:40:58 +0200
> > > > > > >
> > > > > > > Hello Justin,
> > > > > > > I updated to the head of the trunk and relaunched everything. I
> > > > still have a problem with the qpid tools.I can see all the bat files, but
> > > > the code still calls the original files for example:
> > > > > > > 1: run_acl_tests: Calling 'qpid-python-test --broker localhost:63666
> > > > --time -m acl -Dport-i=63668 -Dport-u=63710 -Dport-q=63712
> > > > -Dpolicy-file=D:\qpid-cpp-trunk.git\qpid\qpid\cpp\build-dir-RelWithDebInfo\src\tests\policy.acl'1:
> > > > 'qpid-python-test' is not recognized as an internal or external command,
> > > > > > > All the .py files have not been updated to launch
> > > > qpid-python-test.bat when on windows:Example:
> > > > qpid/cpp/src/tests/run_interop_testscall("qpid-python-test -m interop_tests
> > > > -DOUTDIR={0}", WORK_DIR)
> > > > > > > Regards,Adel
> > > > > > > > Date: Thu, 26 May 2016 15:02:59 -0700
> > > > > > > > Subject: Re: Qpid C++ 0.34 unit tests are failing with visual
> > > > studio 2013
> > > > > > > > From: justin.ross@gmail.com
> > > > > > > > To: users@qpid.apache.org
> > > > > > > >
> > > > > > > > An update. I think I've fixed the python and backslash problems.
> > > > > > > >
> > > > > > > > https://issues.apache.org/jira/browse/QPID-7281
> > > > > > > >
> > > > > > > > Here's what I get now in appveyor:
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > https://ci.appveyor.com/project/ssorj/qpid-svn-reorg/build/hammerandtong.71
> > > > > > > >
> > > > > > > > The unit_test failure is one I've had for a long time. I've not
> > > > yet been
> > > > > > > > able to convince either appveyor to use "localhost" for its
> > > > hostname or
> > > > > > > > unit_test to use "appveyor-vm" as its ssl cert name. So it times
> > > > out.
> > > > > > > >
> > > > > > > > The other tests are running now, with some failures. Note that up
> > > > to now
> > > > > > > > I've been liberal in enabling the cross-platform tests that can
> > > > > > > > hypothetically work in windows. There may be specific instances
> > > > where I'm
> > > > > > > > wrong, and we'll need to adjust the target platform for the test.
> > > > > > > >
> > > > > > > > On Thu, May 26, 2016 at 9:45 AM, Andrew Stitcher <
> > > > astitcher@redhat.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > On Thu, 2016-05-26 at 09:38 -0700, Justin Ross wrote:
> > > > > > > > > > I tried this approach first. I wasn't able to make that
> > > > > > > > > > configuration
> > > > > > > > > > available in CTestCustom.cmake when I tried last. However, I
> > > > don't
> > > > > > > > > > think I
> > > > > > > > > > tried repeating the find_package logic directly in the
> > > > custom.cmake
> > > > > > > > > > file,
> > > > > > > > > > which I will do.
> > > > > > > > >
> > > > > > > > > CMake is hierarchical so the find_package() would need to be in
> > > > a CMake
> > > > > > > > > file above the relevant one (and perhaps in the sequence before
> > > > the
> > > > > > > > > add_directory(..) or include(...) that includes the file you
> > > > want the
> > > > > > > > > definition in - I'm not too clear about that point.
> > > > > > > > >
> > > > > > > > > Andrew
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > ---------------------------------------------------------------------
> > > > > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > > > > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> >
>
RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Adel Boutros <ad...@live.com>.
In env.py.in, all libraries are ".so" extension which will not work on Windows as you will need ".dll" instead
_export_module("HA_LIB", join(BUILD_DIR, "src", "ha.so"))_export_module("XML_LIB", join(BUILD_DIR, "src", "xml.so"))_export_module("AMQP_LIB", join(BUILD_DIR, "src", "amqp.so"))_export_module("TEST_STORE_LIB", join(BUILD_DIR, "src", "tests", "test_store.so"))_export_module("STORE_LIB", join(BUILD_DIR, "src", "linearstore.so"))
> From: adelboutros@live.com
> To: users@qpid.apache.org
> Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> Date: Fri, 27 May 2016 17:49:46 +0200
>
> In qmf_tests, in brokertest.py, there is something wrong with the path because the script cannot find "qpidd" executable. If you add the ".exe" extension then it works.
> I noticed that all other tests use "common.py" for qpidd. So why is this test different?
> Fixing the path makes the test pass and it fixes the same error in other tests.
> Error: AssertionError: executable not found: qpiddFix: qpidd_exec = "qpidd.exe" (In brokertest.py)
> Regards,Adel
>
> > Date: Fri, 27 May 2016 07:59:34 -0700
> > Subject: Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > From: justin.ross@gmail.com
> > To: users@qpid.apache.org
> >
> > Yeah, that's a simple bug on my end. I'll get that fixed and report back.
> >
> > On Fri, May 27, 2016 at 7:52 AM, Adel Boutros <ad...@live.com> wrote:
> >
> > > Also, in env.ps1.in, there is a reference to "$builddir" but it never has
> > > value so the tests needing PYTHON_DIR will always fail.
> > > $PYTHON_DIR="$builddir\python" ---> is interpreted as "\python"
> > > I think there is a missing link between "$builddir" and some Cmake
> > > variable.
> > > > From: adelboutros@live.com
> > > > To: users@qpid.apache.org
> > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > > > Date: Fri, 27 May 2016 16:31:44 +0200
> > > >
> > > > Hello Justin,
> > > > So I launched all the tests and I have 10 failing including the
> > > unit_tests (There is a disconnection error which I can also see in your
> > > appveyor).
> > > >
> > > > The following tests FAILED: 4 - federation_tests (Failed) 5 -
> > > flow_control_tests (Timeout) 6 - ha_tests (Failed) 9 -
> > > python_tests (Failed) 11 - qmf_tests (Failed) 14 -
> > > interlink_tests (Failed) 15 - interop_tests (Timeout) 16 - store_tests
> > > (Failed) 17 - store_tests_clfs (Failed)
> > > > For the store_tests, powershell scripts in current directory cannot be
> > > launched as they are not trusted, so you should add ".\" prior to the
> > > script name.
> > > > C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
> > > "run_store_tests.ps1" "MSSQL"The error message is helpful
> > > actually:run_store_tests.ps1 : The term 'run_store_tests.ps1' is not
> > > recognized as the name of a cmdlet, function... Suggestion [3,General]: The
> > > command run_store_tests.ps1 was not found, but does exist in the current
> > > location. Windows PowerShell does not load commands from the current
> > > location by default. If you trust this command, instead type
> > > ".\run_store_tests.ps1". See "get-help about_Command_Precedence" for more
> > > details.
> > > > I am still debugging the other tests.
> > > > Have you had a better luck than mine?
> > > > I can send you the test logs if you like.
> > > > PS: I am compiling with SASL/SSL disabled and valgrind disabled also
> > > completely.
> > > > Regards,Adel
> > > > > From: adelboutros@live.com
> > > > > To: users@qpid.apache.org
> > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio
> > > 2013
> > > > > Date: Fri, 27 May 2016 12:02:40 +0200
> > > > >
> > > > > Please ignore my last email. There was a problem with the PATH
> > > environment variable.
> > > > >
> > > > > > From: adelboutros@live.com
> > > > > > To: users@qpid.apache.org
> > > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio
> > > 2013
> > > > > > Date: Fri, 27 May 2016 11:40:58 +0200
> > > > > >
> > > > > > Hello Justin,
> > > > > > I updated to the head of the trunk and relaunched everything. I
> > > still have a problem with the qpid tools.I can see all the bat files, but
> > > the code still calls the original files for example:
> > > > > > 1: run_acl_tests: Calling 'qpid-python-test --broker localhost:63666
> > > --time -m acl -Dport-i=63668 -Dport-u=63710 -Dport-q=63712
> > > -Dpolicy-file=D:\qpid-cpp-trunk.git\qpid\qpid\cpp\build-dir-RelWithDebInfo\src\tests\policy.acl'1:
> > > 'qpid-python-test' is not recognized as an internal or external command,
> > > > > > All the .py files have not been updated to launch
> > > qpid-python-test.bat when on windows:Example:
> > > qpid/cpp/src/tests/run_interop_testscall("qpid-python-test -m interop_tests
> > > -DOUTDIR={0}", WORK_DIR)
> > > > > > Regards,Adel
> > > > > > > Date: Thu, 26 May 2016 15:02:59 -0700
> > > > > > > Subject: Re: Qpid C++ 0.34 unit tests are failing with visual
> > > studio 2013
> > > > > > > From: justin.ross@gmail.com
> > > > > > > To: users@qpid.apache.org
> > > > > > >
> > > > > > > An update. I think I've fixed the python and backslash problems.
> > > > > > >
> > > > > > > https://issues.apache.org/jira/browse/QPID-7281
> > > > > > >
> > > > > > > Here's what I get now in appveyor:
> > > > > > >
> > > > > > >
> > > > > > >
> > > https://ci.appveyor.com/project/ssorj/qpid-svn-reorg/build/hammerandtong.71
> > > > > > >
> > > > > > > The unit_test failure is one I've had for a long time. I've not
> > > yet been
> > > > > > > able to convince either appveyor to use "localhost" for its
> > > hostname or
> > > > > > > unit_test to use "appveyor-vm" as its ssl cert name. So it times
> > > out.
> > > > > > >
> > > > > > > The other tests are running now, with some failures. Note that up
> > > to now
> > > > > > > I've been liberal in enabling the cross-platform tests that can
> > > > > > > hypothetically work in windows. There may be specific instances
> > > where I'm
> > > > > > > wrong, and we'll need to adjust the target platform for the test.
> > > > > > >
> > > > > > > On Thu, May 26, 2016 at 9:45 AM, Andrew Stitcher <
> > > astitcher@redhat.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > On Thu, 2016-05-26 at 09:38 -0700, Justin Ross wrote:
> > > > > > > > > I tried this approach first. I wasn't able to make that
> > > > > > > > > configuration
> > > > > > > > > available in CTestCustom.cmake when I tried last. However, I
> > > don't
> > > > > > > > > think I
> > > > > > > > > tried repeating the find_package logic directly in the
> > > custom.cmake
> > > > > > > > > file,
> > > > > > > > > which I will do.
> > > > > > > >
> > > > > > > > CMake is hierarchical so the find_package() would need to be in
> > > a CMake
> > > > > > > > file above the relevant one (and perhaps in the sequence before
> > > the
> > > > > > > > add_directory(..) or include(...) that includes the file you
> > > want the
> > > > > > > > definition in - I'm not too clear about that point.
> > > > > > > >
> > > > > > > > Andrew
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > > > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
>
RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Adel Boutros <ad...@live.com>.
In qmf_tests, in brokertest.py, there is something wrong with the path because the script cannot find "qpidd" executable. If you add the ".exe" extension then it works.
I noticed that all other tests use "common.py" for qpidd. So why is this test different?
Fixing the path makes the test pass and it fixes the same error in other tests.
Error: AssertionError: executable not found: qpiddFix: qpidd_exec = "qpidd.exe" (In brokertest.py)
Regards,Adel
> Date: Fri, 27 May 2016 07:59:34 -0700
> Subject: Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> From: justin.ross@gmail.com
> To: users@qpid.apache.org
>
> Yeah, that's a simple bug on my end. I'll get that fixed and report back.
>
> On Fri, May 27, 2016 at 7:52 AM, Adel Boutros <ad...@live.com> wrote:
>
> > Also, in env.ps1.in, there is a reference to "$builddir" but it never has
> > value so the tests needing PYTHON_DIR will always fail.
> > $PYTHON_DIR="$builddir\python" ---> is interpreted as "\python"
> > I think there is a missing link between "$builddir" and some Cmake
> > variable.
> > > From: adelboutros@live.com
> > > To: users@qpid.apache.org
> > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > > Date: Fri, 27 May 2016 16:31:44 +0200
> > >
> > > Hello Justin,
> > > So I launched all the tests and I have 10 failing including the
> > unit_tests (There is a disconnection error which I can also see in your
> > appveyor).
> > >
> > > The following tests FAILED: 4 - federation_tests (Failed) 5 -
> > flow_control_tests (Timeout) 6 - ha_tests (Failed) 9 -
> > python_tests (Failed) 11 - qmf_tests (Failed) 14 -
> > interlink_tests (Failed) 15 - interop_tests (Timeout) 16 - store_tests
> > (Failed) 17 - store_tests_clfs (Failed)
> > > For the store_tests, powershell scripts in current directory cannot be
> > launched as they are not trusted, so you should add ".\" prior to the
> > script name.
> > > C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
> > "run_store_tests.ps1" "MSSQL"The error message is helpful
> > actually:run_store_tests.ps1 : The term 'run_store_tests.ps1' is not
> > recognized as the name of a cmdlet, function... Suggestion [3,General]: The
> > command run_store_tests.ps1 was not found, but does exist in the current
> > location. Windows PowerShell does not load commands from the current
> > location by default. If you trust this command, instead type
> > ".\run_store_tests.ps1". See "get-help about_Command_Precedence" for more
> > details.
> > > I am still debugging the other tests.
> > > Have you had a better luck than mine?
> > > I can send you the test logs if you like.
> > > PS: I am compiling with SASL/SSL disabled and valgrind disabled also
> > completely.
> > > Regards,Adel
> > > > From: adelboutros@live.com
> > > > To: users@qpid.apache.org
> > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio
> > 2013
> > > > Date: Fri, 27 May 2016 12:02:40 +0200
> > > >
> > > > Please ignore my last email. There was a problem with the PATH
> > environment variable.
> > > >
> > > > > From: adelboutros@live.com
> > > > > To: users@qpid.apache.org
> > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio
> > 2013
> > > > > Date: Fri, 27 May 2016 11:40:58 +0200
> > > > >
> > > > > Hello Justin,
> > > > > I updated to the head of the trunk and relaunched everything. I
> > still have a problem with the qpid tools.I can see all the bat files, but
> > the code still calls the original files for example:
> > > > > 1: run_acl_tests: Calling 'qpid-python-test --broker localhost:63666
> > --time -m acl -Dport-i=63668 -Dport-u=63710 -Dport-q=63712
> > -Dpolicy-file=D:\qpid-cpp-trunk.git\qpid\qpid\cpp\build-dir-RelWithDebInfo\src\tests\policy.acl'1:
> > 'qpid-python-test' is not recognized as an internal or external command,
> > > > > All the .py files have not been updated to launch
> > qpid-python-test.bat when on windows:Example:
> > qpid/cpp/src/tests/run_interop_testscall("qpid-python-test -m interop_tests
> > -DOUTDIR={0}", WORK_DIR)
> > > > > Regards,Adel
> > > > > > Date: Thu, 26 May 2016 15:02:59 -0700
> > > > > > Subject: Re: Qpid C++ 0.34 unit tests are failing with visual
> > studio 2013
> > > > > > From: justin.ross@gmail.com
> > > > > > To: users@qpid.apache.org
> > > > > >
> > > > > > An update. I think I've fixed the python and backslash problems.
> > > > > >
> > > > > > https://issues.apache.org/jira/browse/QPID-7281
> > > > > >
> > > > > > Here's what I get now in appveyor:
> > > > > >
> > > > > >
> > > > > >
> > https://ci.appveyor.com/project/ssorj/qpid-svn-reorg/build/hammerandtong.71
> > > > > >
> > > > > > The unit_test failure is one I've had for a long time. I've not
> > yet been
> > > > > > able to convince either appveyor to use "localhost" for its
> > hostname or
> > > > > > unit_test to use "appveyor-vm" as its ssl cert name. So it times
> > out.
> > > > > >
> > > > > > The other tests are running now, with some failures. Note that up
> > to now
> > > > > > I've been liberal in enabling the cross-platform tests that can
> > > > > > hypothetically work in windows. There may be specific instances
> > where I'm
> > > > > > wrong, and we'll need to adjust the target platform for the test.
> > > > > >
> > > > > > On Thu, May 26, 2016 at 9:45 AM, Andrew Stitcher <
> > astitcher@redhat.com>
> > > > > > wrote:
> > > > > >
> > > > > > > On Thu, 2016-05-26 at 09:38 -0700, Justin Ross wrote:
> > > > > > > > I tried this approach first. I wasn't able to make that
> > > > > > > > configuration
> > > > > > > > available in CTestCustom.cmake when I tried last. However, I
> > don't
> > > > > > > > think I
> > > > > > > > tried repeating the find_package logic directly in the
> > custom.cmake
> > > > > > > > file,
> > > > > > > > which I will do.
> > > > > > >
> > > > > > > CMake is hierarchical so the find_package() would need to be in
> > a CMake
> > > > > > > file above the relevant one (and perhaps in the sequence before
> > the
> > > > > > > add_directory(..) or include(...) that includes the file you
> > want the
> > > > > > > definition in - I'm not too clear about that point.
> > > > > > >
> > > > > > > Andrew
> > > > > > >
> > > > > > >
> > > > > > >
> > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > > > > >
> > > > > > >
> > > > >
> > > >
> > >
> >
> >
Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Justin Ross <ju...@gmail.com>.
Yeah, that's a simple bug on my end. I'll get that fixed and report back.
On Fri, May 27, 2016 at 7:52 AM, Adel Boutros <ad...@live.com> wrote:
> Also, in env.ps1.in, there is a reference to "$builddir" but it never has
> value so the tests needing PYTHON_DIR will always fail.
> $PYTHON_DIR="$builddir\python" ---> is interpreted as "\python"
> I think there is a missing link between "$builddir" and some Cmake
> variable.
> > From: adelboutros@live.com
> > To: users@qpid.apache.org
> > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > Date: Fri, 27 May 2016 16:31:44 +0200
> >
> > Hello Justin,
> > So I launched all the tests and I have 10 failing including the
> unit_tests (There is a disconnection error which I can also see in your
> appveyor).
> >
> > The following tests FAILED: 4 - federation_tests (Failed) 5 -
> flow_control_tests (Timeout) 6 - ha_tests (Failed) 9 -
> python_tests (Failed) 11 - qmf_tests (Failed) 14 -
> interlink_tests (Failed) 15 - interop_tests (Timeout) 16 - store_tests
> (Failed) 17 - store_tests_clfs (Failed)
> > For the store_tests, powershell scripts in current directory cannot be
> launched as they are not trusted, so you should add ".\" prior to the
> script name.
> > C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
> "run_store_tests.ps1" "MSSQL"The error message is helpful
> actually:run_store_tests.ps1 : The term 'run_store_tests.ps1' is not
> recognized as the name of a cmdlet, function... Suggestion [3,General]: The
> command run_store_tests.ps1 was not found, but does exist in the current
> location. Windows PowerShell does not load commands from the current
> location by default. If you trust this command, instead type
> ".\run_store_tests.ps1". See "get-help about_Command_Precedence" for more
> details.
> > I am still debugging the other tests.
> > Have you had a better luck than mine?
> > I can send you the test logs if you like.
> > PS: I am compiling with SASL/SSL disabled and valgrind disabled also
> completely.
> > Regards,Adel
> > > From: adelboutros@live.com
> > > To: users@qpid.apache.org
> > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio
> 2013
> > > Date: Fri, 27 May 2016 12:02:40 +0200
> > >
> > > Please ignore my last email. There was a problem with the PATH
> environment variable.
> > >
> > > > From: adelboutros@live.com
> > > > To: users@qpid.apache.org
> > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio
> 2013
> > > > Date: Fri, 27 May 2016 11:40:58 +0200
> > > >
> > > > Hello Justin,
> > > > I updated to the head of the trunk and relaunched everything. I
> still have a problem with the qpid tools.I can see all the bat files, but
> the code still calls the original files for example:
> > > > 1: run_acl_tests: Calling 'qpid-python-test --broker localhost:63666
> --time -m acl -Dport-i=63668 -Dport-u=63710 -Dport-q=63712
> -Dpolicy-file=D:\qpid-cpp-trunk.git\qpid\qpid\cpp\build-dir-RelWithDebInfo\src\tests\policy.acl'1:
> 'qpid-python-test' is not recognized as an internal or external command,
> > > > All the .py files have not been updated to launch
> qpid-python-test.bat when on windows:Example:
> qpid/cpp/src/tests/run_interop_testscall("qpid-python-test -m interop_tests
> -DOUTDIR={0}", WORK_DIR)
> > > > Regards,Adel
> > > > > Date: Thu, 26 May 2016 15:02:59 -0700
> > > > > Subject: Re: Qpid C++ 0.34 unit tests are failing with visual
> studio 2013
> > > > > From: justin.ross@gmail.com
> > > > > To: users@qpid.apache.org
> > > > >
> > > > > An update. I think I've fixed the python and backslash problems.
> > > > >
> > > > > https://issues.apache.org/jira/browse/QPID-7281
> > > > >
> > > > > Here's what I get now in appveyor:
> > > > >
> > > > >
> > > > >
> https://ci.appveyor.com/project/ssorj/qpid-svn-reorg/build/hammerandtong.71
> > > > >
> > > > > The unit_test failure is one I've had for a long time. I've not
> yet been
> > > > > able to convince either appveyor to use "localhost" for its
> hostname or
> > > > > unit_test to use "appveyor-vm" as its ssl cert name. So it times
> out.
> > > > >
> > > > > The other tests are running now, with some failures. Note that up
> to now
> > > > > I've been liberal in enabling the cross-platform tests that can
> > > > > hypothetically work in windows. There may be specific instances
> where I'm
> > > > > wrong, and we'll need to adjust the target platform for the test.
> > > > >
> > > > > On Thu, May 26, 2016 at 9:45 AM, Andrew Stitcher <
> astitcher@redhat.com>
> > > > > wrote:
> > > > >
> > > > > > On Thu, 2016-05-26 at 09:38 -0700, Justin Ross wrote:
> > > > > > > I tried this approach first. I wasn't able to make that
> > > > > > > configuration
> > > > > > > available in CTestCustom.cmake when I tried last. However, I
> don't
> > > > > > > think I
> > > > > > > tried repeating the find_package logic directly in the
> custom.cmake
> > > > > > > file,
> > > > > > > which I will do.
> > > > > >
> > > > > > CMake is hierarchical so the find_package() would need to be in
> a CMake
> > > > > > file above the relevant one (and perhaps in the sequence before
> the
> > > > > > add_directory(..) or include(...) that includes the file you
> want the
> > > > > > definition in - I'm not too clear about that point.
> > > > > >
> > > > > > Andrew
> > > > > >
> > > > > >
> > > > > >
> ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > > > >
> > > > > >
> > > >
> > >
> >
>
>
RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Adel Boutros <ad...@live.com>.
Also, in env.ps1.in, there is a reference to "$builddir" but it never has value so the tests needing PYTHON_DIR will always fail.
$PYTHON_DIR="$builddir\python" ---> is interpreted as "\python"
I think there is a missing link between "$builddir" and some Cmake variable.
> From: adelboutros@live.com
> To: users@qpid.apache.org
> Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> Date: Fri, 27 May 2016 16:31:44 +0200
>
> Hello Justin,
> So I launched all the tests and I have 10 failing including the unit_tests (There is a disconnection error which I can also see in your appveyor).
>
> The following tests FAILED: 4 - federation_tests (Failed) 5 - flow_control_tests (Timeout) 6 - ha_tests (Failed) 9 - python_tests (Failed) 11 - qmf_tests (Failed) 14 - interlink_tests (Failed) 15 - interop_tests (Timeout) 16 - store_tests (Failed) 17 - store_tests_clfs (Failed)
> For the store_tests, powershell scripts in current directory cannot be launched as they are not trusted, so you should add ".\" prior to the script name.
> C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe "run_store_tests.ps1" "MSSQL"The error message is helpful actually:run_store_tests.ps1 : The term 'run_store_tests.ps1' is not recognized as the name of a cmdlet, function... Suggestion [3,General]: The command run_store_tests.ps1 was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type ".\run_store_tests.ps1". See "get-help about_Command_Precedence" for more details.
> I am still debugging the other tests.
> Have you had a better luck than mine?
> I can send you the test logs if you like.
> PS: I am compiling with SASL/SSL disabled and valgrind disabled also completely.
> Regards,Adel
> > From: adelboutros@live.com
> > To: users@qpid.apache.org
> > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > Date: Fri, 27 May 2016 12:02:40 +0200
> >
> > Please ignore my last email. There was a problem with the PATH environment variable.
> >
> > > From: adelboutros@live.com
> > > To: users@qpid.apache.org
> > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > > Date: Fri, 27 May 2016 11:40:58 +0200
> > >
> > > Hello Justin,
> > > I updated to the head of the trunk and relaunched everything. I still have a problem with the qpid tools.I can see all the bat files, but the code still calls the original files for example:
> > > 1: run_acl_tests: Calling 'qpid-python-test --broker localhost:63666 --time -m acl -Dport-i=63668 -Dport-u=63710 -Dport-q=63712 -Dpolicy-file=D:\qpid-cpp-trunk.git\qpid\qpid\cpp\build-dir-RelWithDebInfo\src\tests\policy.acl'1: 'qpid-python-test' is not recognized as an internal or external command,
> > > All the .py files have not been updated to launch qpid-python-test.bat when on windows:Example: qpid/cpp/src/tests/run_interop_testscall("qpid-python-test -m interop_tests -DOUTDIR={0}", WORK_DIR)
> > > Regards,Adel
> > > > Date: Thu, 26 May 2016 15:02:59 -0700
> > > > Subject: Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > > > From: justin.ross@gmail.com
> > > > To: users@qpid.apache.org
> > > >
> > > > An update. I think I've fixed the python and backslash problems.
> > > >
> > > > https://issues.apache.org/jira/browse/QPID-7281
> > > >
> > > > Here's what I get now in appveyor:
> > > >
> > > >
> > > > https://ci.appveyor.com/project/ssorj/qpid-svn-reorg/build/hammerandtong.71
> > > >
> > > > The unit_test failure is one I've had for a long time. I've not yet been
> > > > able to convince either appveyor to use "localhost" for its hostname or
> > > > unit_test to use "appveyor-vm" as its ssl cert name. So it times out.
> > > >
> > > > The other tests are running now, with some failures. Note that up to now
> > > > I've been liberal in enabling the cross-platform tests that can
> > > > hypothetically work in windows. There may be specific instances where I'm
> > > > wrong, and we'll need to adjust the target platform for the test.
> > > >
> > > > On Thu, May 26, 2016 at 9:45 AM, Andrew Stitcher <as...@redhat.com>
> > > > wrote:
> > > >
> > > > > On Thu, 2016-05-26 at 09:38 -0700, Justin Ross wrote:
> > > > > > I tried this approach first. I wasn't able to make that
> > > > > > configuration
> > > > > > available in CTestCustom.cmake when I tried last. However, I don't
> > > > > > think I
> > > > > > tried repeating the find_package logic directly in the custom.cmake
> > > > > > file,
> > > > > > which I will do.
> > > > >
> > > > > CMake is hierarchical so the find_package() would need to be in a CMake
> > > > > file above the relevant one (and perhaps in the sequence before the
> > > > > add_directory(..) or include(...) that includes the file you want the
> > > > > definition in - I'm not too clear about that point.
> > > > >
> > > > > Andrew
> > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > > >
> > > > >
> > >
> >
>
RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Adel Boutros <ad...@live.com>.
Hello Justin,
So I launched all the tests and I have 10 failing including the unit_tests (There is a disconnection error which I can also see in your appveyor).
The following tests FAILED: 4 - federation_tests (Failed) 5 - flow_control_tests (Timeout) 6 - ha_tests (Failed) 9 - python_tests (Failed) 11 - qmf_tests (Failed) 14 - interlink_tests (Failed) 15 - interop_tests (Timeout) 16 - store_tests (Failed) 17 - store_tests_clfs (Failed)
For the store_tests, powershell scripts in current directory cannot be launched as they are not trusted, so you should add ".\" prior to the script name.
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe "run_store_tests.ps1" "MSSQL"The error message is helpful actually:run_store_tests.ps1 : The term 'run_store_tests.ps1' is not recognized as the name of a cmdlet, function... Suggestion [3,General]: The command run_store_tests.ps1 was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type ".\run_store_tests.ps1". See "get-help about_Command_Precedence" for more details.
I am still debugging the other tests.
Have you had a better luck than mine?
I can send you the test logs if you like.
PS: I am compiling with SASL/SSL disabled and valgrind disabled also completely.
Regards,Adel
> From: adelboutros@live.com
> To: users@qpid.apache.org
> Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> Date: Fri, 27 May 2016 12:02:40 +0200
>
> Please ignore my last email. There was a problem with the PATH environment variable.
>
> > From: adelboutros@live.com
> > To: users@qpid.apache.org
> > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > Date: Fri, 27 May 2016 11:40:58 +0200
> >
> > Hello Justin,
> > I updated to the head of the trunk and relaunched everything. I still have a problem with the qpid tools.I can see all the bat files, but the code still calls the original files for example:
> > 1: run_acl_tests: Calling 'qpid-python-test --broker localhost:63666 --time -m acl -Dport-i=63668 -Dport-u=63710 -Dport-q=63712 -Dpolicy-file=D:\qpid-cpp-trunk.git\qpid\qpid\cpp\build-dir-RelWithDebInfo\src\tests\policy.acl'1: 'qpid-python-test' is not recognized as an internal or external command,
> > All the .py files have not been updated to launch qpid-python-test.bat when on windows:Example: qpid/cpp/src/tests/run_interop_testscall("qpid-python-test -m interop_tests -DOUTDIR={0}", WORK_DIR)
> > Regards,Adel
> > > Date: Thu, 26 May 2016 15:02:59 -0700
> > > Subject: Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > > From: justin.ross@gmail.com
> > > To: users@qpid.apache.org
> > >
> > > An update. I think I've fixed the python and backslash problems.
> > >
> > > https://issues.apache.org/jira/browse/QPID-7281
> > >
> > > Here's what I get now in appveyor:
> > >
> > >
> > > https://ci.appveyor.com/project/ssorj/qpid-svn-reorg/build/hammerandtong.71
> > >
> > > The unit_test failure is one I've had for a long time. I've not yet been
> > > able to convince either appveyor to use "localhost" for its hostname or
> > > unit_test to use "appveyor-vm" as its ssl cert name. So it times out.
> > >
> > > The other tests are running now, with some failures. Note that up to now
> > > I've been liberal in enabling the cross-platform tests that can
> > > hypothetically work in windows. There may be specific instances where I'm
> > > wrong, and we'll need to adjust the target platform for the test.
> > >
> > > On Thu, May 26, 2016 at 9:45 AM, Andrew Stitcher <as...@redhat.com>
> > > wrote:
> > >
> > > > On Thu, 2016-05-26 at 09:38 -0700, Justin Ross wrote:
> > > > > I tried this approach first. I wasn't able to make that
> > > > > configuration
> > > > > available in CTestCustom.cmake when I tried last. However, I don't
> > > > > think I
> > > > > tried repeating the find_package logic directly in the custom.cmake
> > > > > file,
> > > > > which I will do.
> > > >
> > > > CMake is hierarchical so the find_package() would need to be in a CMake
> > > > file above the relevant one (and perhaps in the sequence before the
> > > > add_directory(..) or include(...) that includes the file you want the
> > > > definition in - I'm not too clear about that point.
> > > >
> > > > Andrew
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > >
> > > >
> >
>
RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Adel Boutros <ad...@live.com>.
Please ignore my last email. There was a problem with the PATH environment variable.
> From: adelboutros@live.com
> To: users@qpid.apache.org
> Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> Date: Fri, 27 May 2016 11:40:58 +0200
>
> Hello Justin,
> I updated to the head of the trunk and relaunched everything. I still have a problem with the qpid tools.I can see all the bat files, but the code still calls the original files for example:
> 1: run_acl_tests: Calling 'qpid-python-test --broker localhost:63666 --time -m acl -Dport-i=63668 -Dport-u=63710 -Dport-q=63712 -Dpolicy-file=D:\qpid-cpp-trunk.git\qpid\qpid\cpp\build-dir-RelWithDebInfo\src\tests\policy.acl'1: 'qpid-python-test' is not recognized as an internal or external command,
> All the .py files have not been updated to launch qpid-python-test.bat when on windows:Example: qpid/cpp/src/tests/run_interop_testscall("qpid-python-test -m interop_tests -DOUTDIR={0}", WORK_DIR)
> Regards,Adel
> > Date: Thu, 26 May 2016 15:02:59 -0700
> > Subject: Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > From: justin.ross@gmail.com
> > To: users@qpid.apache.org
> >
> > An update. I think I've fixed the python and backslash problems.
> >
> > https://issues.apache.org/jira/browse/QPID-7281
> >
> > Here's what I get now in appveyor:
> >
> >
> > https://ci.appveyor.com/project/ssorj/qpid-svn-reorg/build/hammerandtong.71
> >
> > The unit_test failure is one I've had for a long time. I've not yet been
> > able to convince either appveyor to use "localhost" for its hostname or
> > unit_test to use "appveyor-vm" as its ssl cert name. So it times out.
> >
> > The other tests are running now, with some failures. Note that up to now
> > I've been liberal in enabling the cross-platform tests that can
> > hypothetically work in windows. There may be specific instances where I'm
> > wrong, and we'll need to adjust the target platform for the test.
> >
> > On Thu, May 26, 2016 at 9:45 AM, Andrew Stitcher <as...@redhat.com>
> > wrote:
> >
> > > On Thu, 2016-05-26 at 09:38 -0700, Justin Ross wrote:
> > > > I tried this approach first. I wasn't able to make that
> > > > configuration
> > > > available in CTestCustom.cmake when I tried last. However, I don't
> > > > think I
> > > > tried repeating the find_package logic directly in the custom.cmake
> > > > file,
> > > > which I will do.
> > >
> > > CMake is hierarchical so the find_package() would need to be in a CMake
> > > file above the relevant one (and perhaps in the sequence before the
> > > add_directory(..) or include(...) that includes the file you want the
> > > definition in - I'm not too clear about that point.
> > >
> > > Andrew
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > For additional commands, e-mail: users-help@qpid.apache.org
> > >
> > >
>
RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Adel Boutros <ad...@live.com>.
Hello Justin,
I updated to the head of the trunk and relaunched everything. I still have a problem with the qpid tools.I can see all the bat files, but the code still calls the original files for example:
1: run_acl_tests: Calling 'qpid-python-test --broker localhost:63666 --time -m acl -Dport-i=63668 -Dport-u=63710 -Dport-q=63712 -Dpolicy-file=D:\qpid-cpp-trunk.git\qpid\qpid\cpp\build-dir-RelWithDebInfo\src\tests\policy.acl'1: 'qpid-python-test' is not recognized as an internal or external command,
All the .py files have not been updated to launch qpid-python-test.bat when on windows:Example: qpid/cpp/src/tests/run_interop_testscall("qpid-python-test -m interop_tests -DOUTDIR={0}", WORK_DIR)
Regards,Adel
> Date: Thu, 26 May 2016 15:02:59 -0700
> Subject: Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> From: justin.ross@gmail.com
> To: users@qpid.apache.org
>
> An update. I think I've fixed the python and backslash problems.
>
> https://issues.apache.org/jira/browse/QPID-7281
>
> Here's what I get now in appveyor:
>
>
> https://ci.appveyor.com/project/ssorj/qpid-svn-reorg/build/hammerandtong.71
>
> The unit_test failure is one I've had for a long time. I've not yet been
> able to convince either appveyor to use "localhost" for its hostname or
> unit_test to use "appveyor-vm" as its ssl cert name. So it times out.
>
> The other tests are running now, with some failures. Note that up to now
> I've been liberal in enabling the cross-platform tests that can
> hypothetically work in windows. There may be specific instances where I'm
> wrong, and we'll need to adjust the target platform for the test.
>
> On Thu, May 26, 2016 at 9:45 AM, Andrew Stitcher <as...@redhat.com>
> wrote:
>
> > On Thu, 2016-05-26 at 09:38 -0700, Justin Ross wrote:
> > > I tried this approach first. I wasn't able to make that
> > > configuration
> > > available in CTestCustom.cmake when I tried last. However, I don't
> > > think I
> > > tried repeating the find_package logic directly in the custom.cmake
> > > file,
> > > which I will do.
> >
> > CMake is hierarchical so the find_package() would need to be in a CMake
> > file above the relevant one (and perhaps in the sequence before the
> > add_directory(..) or include(...) that includes the file you want the
> > definition in - I'm not too clear about that point.
> >
> > Andrew
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > For additional commands, e-mail: users-help@qpid.apache.org
> >
> >
Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Justin Ross <ju...@gmail.com>.
An update. I think I've fixed the python and backslash problems.
https://issues.apache.org/jira/browse/QPID-7281
Here's what I get now in appveyor:
https://ci.appveyor.com/project/ssorj/qpid-svn-reorg/build/hammerandtong.71
The unit_test failure is one I've had for a long time. I've not yet been
able to convince either appveyor to use "localhost" for its hostname or
unit_test to use "appveyor-vm" as its ssl cert name. So it times out.
The other tests are running now, with some failures. Note that up to now
I've been liberal in enabling the cross-platform tests that can
hypothetically work in windows. There may be specific instances where I'm
wrong, and we'll need to adjust the target platform for the test.
On Thu, May 26, 2016 at 9:45 AM, Andrew Stitcher <as...@redhat.com>
wrote:
> On Thu, 2016-05-26 at 09:38 -0700, Justin Ross wrote:
> > I tried this approach first. I wasn't able to make that
> > configuration
> > available in CTestCustom.cmake when I tried last. However, I don't
> > think I
> > tried repeating the find_package logic directly in the custom.cmake
> > file,
> > which I will do.
>
> CMake is hierarchical so the find_package() would need to be in a CMake
> file above the relevant one (and perhaps in the sequence before the
> add_directory(..) or include(...) that includes the file you want the
> definition in - I'm not too clear about that point.
>
> Andrew
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Andrew Stitcher <as...@redhat.com>.
On Thu, 2016-05-26 at 09:38 -0700, Justin Ross wrote:
> I tried this approach first.��I wasn't able to make that
> configuration
> available in CTestCustom.cmake when I tried last.��However, I don't
> think I
> tried repeating the find_package logic directly in the custom.cmake
> file,
> which I will do.
CMake is hierarchical so the find_package() would need to be in a CMake
file above the relevant one (and perhaps in the sequence before the
add_directory(..) or include(...) that includes the file you want the
definition in - I'm not too clear about that point.
Andrew
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Justin Ross <ju...@gmail.com>.
I tried this approach first. I wasn't able to make that configuration
available in CTestCustom.cmake when I tried last. However, I don't think I
tried repeating the find_package logic directly in the custom.cmake file,
which I will do.
On Thu, May 26, 2016 at 9:21 AM, Andrew Stitcher <as...@redhat.com>
wrote:
> On Mon, 2016-05-23 at 05:52 -0700, Justin Ross wrote:
> > ...
> > > 2) Python scripts can be executed on Linux without adding "python"
> > > prior
> > > to the script name because it is detected from the first line in
> > > the script
> > > (#!/usr/bin/env python). This doesn't work on Windows unless "py"
> > > extension
> > > files are associated with python. To do this, all python scripts
> > > must end
> > > with .py which is not the case for a lot of the scripts such as the
> > > qpidd
> > > management tools (qpid-python-test, qpid-config, ...)
> > >
>
> There is a simple solution for this issue (which is what we do with the
> proton tests) I'm a little surprised we don't use it here:
>
> find_package(Python ...)
>
> - I'm pretty sure this is already in the Qpid Cmake build somewhere
> - This sets up a bunch of useful variables if it finds python including
> PYTHON_EXECUTABLE.
>
> Followed by:
>
> add_test(... ${PYTHON_EXECUTABLE} python_script ...)
>
> If you want to call a python script directly there is no need for an
> intermediate shell/cmd/powershell script - this is why we were moving
> Qpid testing over to being driven by python scripts.
>
> > The tests wrt Windows have long been a problem. I started working on
> > improving them a couple months ago. One of the things I did was add
> > batch
> > files for all the command line tools so that the test scripts could
> > more
> > easily use them.
>
> If the scripts are to be used inside other test scripts this is more of
> a problem, but I'd suggest the more canonical Windows solution would be
> to create .py files as well as unadorned names (either copies or
> links). This way there is no extra script just the original one with a
> slightly different name.
>
> Equally, given these are our own test scripts, we can amend them to add
> the implied invocation of python, remembering that we will need to
> allow python to be in an arbitrary place, so we need to use
> ${PYTHON_EXECUTABLE} and set it up for the tests.
>
> Andrew
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Andrew Stitcher <as...@redhat.com>.
On Mon, 2016-05-23 at 05:52 -0700, Justin Ross wrote:
> ...
> > 2) Python scripts can be executed on Linux without adding "python"
> > prior
> > to the script name because it is detected from the first line in
> > the script
> > (#!/usr/bin/env python). This doesn't work on Windows unless "py"
> > extension
> > files are associated with python. To do this, all python scripts
> > must end
> > with .py which is not the case for a lot of the scripts such as the
> > qpidd
> > management tools (qpid-python-test, qpid-config, ...)
> >
There is a simple solution for this issue (which is what we do with the
proton tests) I'm a little surprised we don't use it here:
find_package(Python ...)
- I'm pretty sure this is already in the Qpid Cmake build somewhere
- This sets up a bunch of useful variables if it finds python including
PYTHON_EXECUTABLE.
Followed by:
add_test(... ${PYTHON_EXECUTABLE} python_script ...)
If you want to call a python script directly there is no need for an
intermediate shell/cmd/powershell script - this is why we were moving
Qpid testing over to being driven by python scripts.
> The tests wrt Windows have long been a problem.��I started working on
> improving them a couple months ago.��One of the things I did was add
> batch
> files for all the command line tools so that the test scripts could
> more
> easily use them.
If the scripts are to be used inside other test scripts this is more of
a problem, but I'd suggest the more canonical Windows solution would be
to create .py files as well as unadorned names (either copies or
links). This way there is no extra script just the original one with a
slightly different name.
Equally, given these are our own test scripts, we can amend them to add
the implied invocation of python, remembering that we will need to
allow python to be in an arbitrary place, so we need to use
${PYTHON_EXECUTABLE} and set it up for the tests.
Andrew
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by Justin Ross <ju...@gmail.com>.
On Mon, May 23, 2016 at 4:12 AM, <ad...@live.com> wrote:
> 1) A missing powershell script(run_queue_redirect.ps1) forces a test
> (queue_redirect) not to start
>
Given that it's not really in working shape, I would disable this test.
Otherwise, you'll need to write the missing script. Even if you do write
the missing script, there's no guarantee the test will work as expected,
just because it wasn't ported to windows before and hasn't historically
been under test.
> 2) Python scripts can be executed on Linux without adding "python" prior
> to the script name because it is detected from the first line in the script
> (#!/usr/bin/env python). This doesn't work on Windows unless "py" extension
> files are associated with python. To do this, all python scripts must end
> with .py which is not the case for a lot of the scripts such as the qpidd
> management tools (qpid-python-test, qpid-config, ...)
>
The tests wrt Windows have long been a problem. I started working on
improving them a couple months ago. One of the things I did was add batch
files for all the command line tools so that the test scripts could more
easily use them.
https://github.com/apache/qpid/blob/trunk/qpid/cpp/management/python/bin/qpid-config.bat
That work is on trunk right now, set for release in Qpid C++ 1.35.0.
That's coming in a month or so.
> So we wanted to know if you could help us fix the above issues?
>
> We are currently debugging other issues as well and wanted to ask you to
> confirm that some of the tests actually requires the management tools
> installed as a pre-requisite?
>
That's right. Many of the tests require the management tools. As of
1.35.0, those tools are part of the C++ source tree.
Care to try running the trunk tests? The changes there will address some
of your problems, but there are definitely still known problems. I'd love
to get your help to improve our tests in the next release.
Justin
Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Posted by ad...@live.com.
Hello guys,
We were able to advance on this issue by changing the machine and using one with less security restraints.
Now we have the following issues:
1) A missing powershell script(run_queue_redirect.ps1) forces a test (queue_redirect) not to start
2) Python scripts can be executed on Linux without adding "python" prior to the script name because it is detected from the first line in the script (#!/usr/bin/env python). This doesn't work on Windows unless "py" extension files are associated with python. To do this, all python scripts must end with .py which is not the case for a lot of the scripts such as the qpidd management tools (qpid-python-test, qpid-config, ...)
So we wanted to know if you could help us fix the above issues?
We are currently debugging other issues as well and wanted to ask you to confirm that some of the tests actually requires the management tools installed as a pre-requisite?
Regards,
Adel
From: Rabih M
Sent: Wednesday, May 18, 16:54
Subject: Qpid C++ 0.34 unit tests are failing with visual studio 2013
To: users@qpid.apache.org
Hello,
I compiled the Qpid C++ code on windows using visual studio 2013.
I have some unit tests failures, I tried to debug but it is not obvious to
find the root cause.
In qpid-client-test: The client is not able to connect to the qpid broker.
This the output I am getting:
...
test 1
Start 1: qpid-client-test
1: Test command: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
D:/qpid-cpp-0.34/qpid-cpp-0.34/qpid/cpp/src/tests/run_test.ps1 -buildDir
D:/qpid-cpp-0.34/qpid-cpp-0.34/qpid/cpp/build-dir -startBroker --
D:/qpid-cpp-0.34/qpid-cpp-0.34/qpid/cpp/build-dir/src/tests/qpid-client-test.exe
1: Test timeout computed to be: 1500
1: 2016-05-18 16:46:39 [Broker] notice Broker (pid=10372) start-up
1: 2016-05-18 16:46:39 [Broker] notice SASL disabled: No Authentication
Performed
1: 2016-05-18 16:46:39 [Security] notice Listening for SSL connections on
TCP port 5671
1: 2016-05-18 16:46:39 [Network] notice Listening on TCP/TCP6 port 21077
1: 2016-05-18 16:46:40 [Network] warning Connect failed: No connection
could be made because the target machine actively refused it. :
localhost:21077
(D:\qpid-cpp-0.34\qpid-cpp-0.34\qpid\cpp\src\qpid\sys\windows\WinSocket.cpp:164)
1: Connection closed
1: WARNING: suspicious log entries in
D:\qpid-cpp-0.34\qpid-cpp-0.34\qpid\cpp\build-dir\src\tests\qpid-client-test.log:1:2016-05-18
16:46:40 [Network] warning Connect failed: No connection could be made
because the target machine actively refused it. : localhost:21077
(D:\qpid-cpp-0.34\qpid-cpp-0.34\qpid\cpp\src\qpid\sys\windows\WinSocket.cpp:164)
1: 2016-05-18 16:46:40 [Broker] notice Broker (pid=10372) shut-down
1/1 Test #1: qpid-client-test .................***Failed 2.15 sec
Did anyone encountered this error before?
The firewall on the machine is off. And I verified using netstat that the
port 21077 was open and listening.
Thanks,
Rabih