Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Message-ID: <DUB112-W13421539DCAA9F4FFB68614CD4E0@phx.gbl>
Content-Type: multipart/alternative;
	boundary="_cf6fa43a-5d8f-48a7-9aa1-2be8504d522b_"
From: Adel Boutros <adelboutros@live.com>
To: "users@qpid.apache.org" <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
Importance: Normal
In-Reply-To: 
 <CANVjZ_T5yRJ1nXz9q8Ec2WeJ3bDDG-Sn6HgEA_ezOJBxEUw_FA@mail.gmail.com>
References: 
 <CAHFPYGZ1pNeu+Zsp2pT+mM7ieoM4-DdKOLUcMoRHr-qdgePAxQ@mail.gmail.com>,<DUB408-EAS102D2627B51F802E2FD713ECD4E0@phx.gbl>,<CANVjZ_T5yRJ1nXz9q8Ec2WeJ3bDDG-Sn6HgEA_ezOJBxEUw_FA@mail.gmail.com>
MIME-Version: 1.0
archived-at: Mon, 23 May 2016 13:51:39 -0000

--_cf6fa43a-5d8f-48a7-9aa1-2be8504d522b_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Yes sure=2C we can try to launch them on the trunk. I will let you know whe=
n this is done and how it turns out.
For the time being=2C we will stick with the already passing tests: 1/25 Te=
st  #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: quic=
k_txtest .....................   Passed    1.01 sec 5/25 Test  #5: quick_tx=
test2 ....................   Passed    0.99 sec 6/25 Test  #6: msg_group_te=
sts ..................   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 ...............***Fai=
led    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 sec1=
8/25 Test #18: queue_flow_limit_tests ...........   Passed    1.37 sec19/25=
 Test #19: acl_tests ........................***Failed   20.30 sec20/25 Tes=
t #20: cli_tests ........................***Failed    0.37 sec21/25 Test #2=
1: dynamic_log_level_test ...........***Failed    0.33 sec22/25 Test #22: d=
ynamic_log_hires_timestamp ......***Failed    0.31 sec23/25 Test #23: store=
_tests ......................***Failed  153.19 sec24/25 Test #24: store_tes=
ts_clfs .................***Failed  153.92 sec25/25 Test #25: queue_redirec=
t ...................***Failed    0.37 sec
PS: The ha_tests have a missing dependency but is marked as passed.
Regards=2CAdel

> Date: Mon=2C 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
>=20
> On Mon=2C May 23=2C 2016 at 4:12 AM=2C <adelboutros@live.com> wrote:
>=20
> > 1) A missing powershell script(run_queue_redirect.ps1) forces a test
> > (queue_redirect) not to start
> >
>=20
> Given that it's not really in working shape=2C I would disable this test.
> Otherwise=2C you'll need to write the missing script.  Even if you do wri=
te
> the missing script=2C there's no guarantee the test will work as expected=
=2C
> just because it wasn't ported to windows before and hasn't historically
> been under test.
>=20
>=20
> > 2) Python scripts can be executed on Linux without adding "python" prio=
r
> > to the script name because it is detected from the first line in the sc=
ript
> > (#!/usr/bin/env python). This doesn't work on Windows unless "py" exten=
sion
> > files are associated with python. To do this=2C all python scripts must=
 end
> > with .py which is not the case for a lot of the scripts such as the qpi=
dd
> > management tools (qpid-python-test=2C qpid-config=2C ...)
> >
>=20
> 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 batc=
h
> files for all the command line tools so that the test scripts could more
> easily use them.
>=20
> https://github.com/apache/qpid/blob/trunk/qpid/cpp/management/python/bin/=
qpid-config.bat
>=20
> That work is on trunk right now=2C set for release in Qpid C++ 1.35.0.
> That's coming in a month or so.
>=20
>=20
> > 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 t=
o
> > confirm that some of the tests actually requires the management tools
> > installed as a pre-requisite?
> >
>=20
> That's right.  Many of the tests require the management tools.  As of
> 1.35.0=2C those tools are part of the C++ source tree.
>=20
> Care to try running the trunk tests?  The changes there will address some
> of your problems=2C but there are definitely still known problems.  I'd l=
ove
> to get your help to improve our tests in the next release.
>=20
> Justin
 		 	   		  =

--_cf6fa43a-5d8f-48a7-9aa1-2be8504d522b_--