Is there something I can do to improve or expedite the process of pulling my changes?
Geoffrey Viola SOFTWARE ENGINEER asirobots.com -----Original Message----- From: Geoffrey Viola Sent: Monday, February 23, 2015 11:11 AM To: 'Brad King' Cc: [email protected] Subject: RE: FW: [cmake-developers] Initial Attempt at Green Hill MULTI IDE Generator Support >Please also add: > > set(dashboard_cache " > CMake_TEST_GreenHillsMULTI:BOOL=ON > ") > >to the nightly script so that the tests will run once we integrate them into >'next' for testing. That line has been added to the nightly script. It might be interesting to note that in the experimental build I manually rewrite the CMakeCache, because it does not use the "write_cache" macro found in cmake_common.cmake. Here is what works for that script: file(READ "${CMAKE_CACHE_FILENAME}" localCache) if (NOT "${localCache}" MATCHES ".*CMake_TEST_GreenHillsMULTI.*") file(APPEND "${CMAKE_CACHE_FILENAME}" " CMake_TEST_GreenHillsMULTI:BOOL=ON ") endif() >> My nightly build passes 50% of the time. > >Many of our nightly test machines have sporadic failures of a few tests due to >locally transient conditions or races in the native tools. We've learned to >tolerate them. Don't worry about those. Sounds good. I reran the tests this morning and they all passed. Geoffrey Viola SOFTWARE ENGINEER asirobots.com -----Original Message----- From: Brad King [mailto:[email protected]] Sent: Monday, February 23, 2015 10:52 AM To: Geoffrey Viola Cc: [email protected] Subject: Re: FW: [cmake-developers] Initial Attempt at Green Hill MULTI IDE Generator Support On 02/23/2015 11:44 AM, Geoffrey Viola wrote: > I added "set(ENV{PATH})" to clear my path Good, I'm glad that helped. However, I'm surprised a completely empty path works. Typically I at least include the Windows system directories: set(ENV{PATH} "c:\\Windows\\system32;c:\\Windows") Please also add: set(dashboard_cache " CMake_TEST_GreenHillsMULTI:BOOL=ON ") to the nightly script so that the tests will run once we integrate them into 'next' for testing. > My nightly build passes 50% of the time. Many of our nightly test machines have sporadic failures of a few tests due to locally transient conditions or races in the native tools. We've learned to tolerate them. Don't worry about those. Thanks, -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. -- 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-developers
