On Mon, May 23, 2016 at 4:12 AM, <[email protected]> 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
