As demonstrated here https://github.com/QIICR/dcmqi/pull/79, the problem is resolved when .cmd versions of the commands are used.
On Wed, Aug 24, 2016 at 1:10 PM, Andrey Fedorov <[email protected]> wrote: > Hi, > > we are running ctest's on appveyor using npm-installed packages. > Specifically, we run jsonlint and ajv on json files to validate the > content. > > Packages are installed in this line: > https://github.com/QIICR/dcmqi/blob/master/appveyor.yml#L12-L13 of the > appveyor configuration. > > The installed packages can be run wihtout problems when invoked > directly from command line on appveyor. These lines > https://github.com/QIICR/dcmqi/blob/master/appveyor.yml#L35-L36 both > work fine on appveyor: > https://ci.appveyor.com/project/fedorov/dcmqi/build/0.0.251#L1203. > > The path to the ajv package used by ctest is identical to the one that > works when invoked directly from the cmd shell; here is the location > where ctest is > invoked:https://github.com/QIICR/dcmqi/blob/master/appveyor.yml#L37, > and this is the where it is being run by appveyor: > https://ci.appveyor.com/project/fedorov/dcmqi/build/0.0.251#L1662. > > Bottom line: ajv works when invoked directly from the appveyor windows > cmd shell, but not when called by ctest. > > Why is ctest failing to run the test with "Not Run/BAD_COMMAND" status? > > AF -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
