[cmake-developers] FW: Initial Attempt at Green Hill MULTI IDE Generator Support

[Geoffrey Viola]

>> Please add to your dashboard scripts a line like:
>>
>> set(ENV{PATH} ...)
>>
>> to set a path without python in it for running this dashboard.
>...
>>> Also, I haven't debugged the warnings in the Build row yet.
>>
>> That may be due to the lack of a fresh build tree:
>>
>> #CTEST_EMPTY_BINARY_DIRECTORY(${CTEST_BINARY_DIRECTORY})
>
>I'll give it a try this weekend.

I added "set(ENV{PATH})" to clear my path in both the experimental and nightly builds. That seems to have fixed some of my issues.

I have my experimental build passing: https://open.cdash.org/viewTest.php?onlypassed&buildid=3704247. My nightly build passes 50% of the time. Here's it passing https://open.cdash.org/viewTest.php?onlypassed&buildid=3704273. Here's it failing https://open.cdash.org/buildSummary.php?buildid=3706323. I'm still debugging the sporadic test failures for the nightly build. The computer might be lacking resources.


Geoffrey Viola
SOFTWARE ENGINEER
asirobots.com



-----Original Message-----
From: Geoffrey Viola
Sent: Friday, February 20, 2015 8:56 AM
To: 'Brad King'
Cc: cmake-developers at cmake.org
Subject: RE: [cmake-developers] Initial Attempt at Green Hill MULTI IDE Generator Support

>> But I still get the "CMake.GetPrerequisites" test timing out.
>
> I don't see that in:
>
> https://open.cdash.org/buildSummary.php?buildid=3701966

You're right. For some reason it is not timing out. It just takes a really long time. I wonder if my path is long. That test takes an order of magnitude longer on my machine than the rest: https://open.cdash.org/testSummary.php?project=1&name=CMake.GetPrerequisites&date=2015-02-19.

> Please add to your dashboard scripts a line like:
>
> set(ENV{PATH} ...)
>
> to set a path without python in it for running this dashboard.
...
>> Also, I haven't debugged the warnings in the Build row yet.
>
> That may be due to the lack of a fresh build tree:
>
> #CTEST_EMPTY_BINARY_DIRECTORY(${CTEST_BINARY_DIRECTORY})

I'll give it a try this weekend.


Geoffrey Viola
SOFTWARE ENGINEER
asirobots.com



-----Original Message-----
From: Brad King [mailto:brad.king at kitware.com]
Sent: Friday, February 20, 2015 8:35 AM
To: Geoffrey Viola
Cc: cmake-developers at cmake.org
Subject: Re: [cmake-developers] Initial Attempt at Green Hill MULTI IDE Generator Support

On 02/19/2015 07:44 PM, Geoffrey Viola wrote:
> The nightly build that I use does use the "cmake_common.cmake" script
> to grab the latest code, build, test it, etc. Here's what my nightly
> build results look like: https://open.cdash.org/buildSummary.php?buildid=3701008.

Sorry, I mixed up your nightly build and the experimental build you linked.

> I made that small change in the attached patch.
> I ran another experimental build in debug. Here are those results:
> https://open.cdash.org/buildSummary.php?buildid=3701457.

Thanks.

> I expected the "CMakeOnly.MajorVersionSelection-PythonInterp_2" to
> fail because I have the Python 3.3 executable in my path.

Please add to your dashboard scripts a line like:

 set(ENV{PATH} ...)

to set a path without python in it for running this dashboard.
That will avoid the problem, which is a separate discussion to address.  (The test is covering that the requested major version is preferred if executables called "python2" and "python3" are both in the path, but if just "python" is available then it is
used.)

> But I still get the "CMake.GetPrerequisites" test timing out.

I don't see that in:

 https://open.cdash.org/buildSummary.php?buildid=3701966

> Also, I haven't debugged the warnings in the Build row yet.

That may be due to the lack of a fresh build tree:

 #CTEST_EMPTY_BINARY_DIRECTORY(${CTEST_BINARY_DIRECTORY})

> This suit of tests was done using a script based on the autogenerated
> "CTestScript.cmake" script.

I don't think CDash has been configured to generate those for CMake properly.  Once you have the nightly dashboard submission running cleanly then we can look at merging your generator for testing in 'next' to have it covered there.

-Brad

This message contains confidential information and is intended only for the recipient. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately if you have received this e-mail by mistake and delete this e-mail from your system. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.