[cmake-developers] Any idea why continuous tests are failing?

[David Cole]

But this must mean that the Run CMake tests are using the wrong cmake
for the tests..... It should use the newly-built CMake for running the
test, which should have the new policy in it.

Your "if policy" commit here, should not be necessary:

  http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d12fdf5303e6ec43ce68207fb05487bf705e8e73


On Thu, Nov 22, 2012 at 11:50 AM, Stephen Kelly <steveire at gmail.com> wrote:
> Stephen Kelly wrote:
>
>>
>> Hi,
>>
>> After my merge today, the continuous tests for Borland and WinSDK started
>> to fail with exit code 1 in my new unit test:
>>
>>  http://open.cdash.org/testDetails.php?test=167420134&build=2677125
>>  http://open.cdash.org/testDetails.php?test=167423128&build=2677205
>>
>> I've inspected the code again, and I don't know why it is failing and why
>> only those two are failing. Any guesses?
>
> I think it was a result of using an old cmake/ctest to test the new one, so
> the policy under test was not in the old cmake. Seems to be fixed now.
>
> Thanks,
>
> Steve.
>
>
> --
>
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers