qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <adelbout...@live.com>
Subject Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Date Mon, 23 May 2016 11:12:25 GMT


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



Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message