On 23.10.2015 16:52, Brad King wrote:
Thanks. Fixed:
CTest: Fix regression in handling of a RUN_SERIAL test that fails
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e61973e1
I've queued this for merge to 'release' for 3.4.0-rc3.
-Brad
Thanks!
Nils
--
Powered by www.kitware.com
Le 23/10/15 11:22, Nils Gladitz a écrit :
Given this test case:
cmake_minimum_required(VERSION 3.3)
project(Foo NONE)
install(FILES CMakeLists.txt DESTINATION tmp)
set(CPACK_DEBIAN_COMPRESSION_TYPE "xz")
set(CPACK_PACKAGE_CONTACT "f...@bar.com")
include(CPack)
A debian
Given this test case:
cmake_minimum_required(VERSION 3.3)
project(Foo NONE)
install(FILES CMakeLists.txt DESTINATION tmp)
set(CPACK_DEBIAN_COMPRESSION_TYPE "xz")
set(CPACK_PACKAGE_CONTACT "f...@bar.com")
include(CPack)
A debian package created with:
cpack -G DEB
Fails during
On 10/23/2015 06:04 AM, Raffi Enficiaud wrote:
> Fix attached! (based on current master a03c13a)
Thanks. I backported it to 'release' and applied:
CPackDEB: Use proper compression scheme for control.tar.gz
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=66178ae5
> PS.: I will add the
On 10/23/2015 03:23 AM, Nils Gladitz wrote:
> I reduced it to this test case:
>
>cmake_minimum_required(VERSION 3.4)
>
>project(Foo NONE)
>
>enable_testing()
>
>add_test(NAME foo COMMAND command_not_found)
>set_property(TEST foo PROPERTY RUN_SERIAL ON)
>
>add_test(NAME
I switched from 3.2.1 to 3.4.0-rc2 on a Windows and a Linux dashboard
client for a custom project.
On the Linux client parallel testing now loops with 100% CPU somewhere
in cmCTestMultiProcessHandler::StartNextTests and
cmCTestMultiProcessHandler::CheckOutput.
I don't have a proper stack
On 10/23/2015 09:10 AM, Nils Gladitz wrote:
I switched from 3.2.1 to 3.4.0-rc2 on a Windows and a Linux dashboard
client for a custom project.
On the Linux client parallel testing now loops with 100% CPU somewhere
in cmCTestMultiProcessHandler::StartNextTests and
On 08/10/15 02:37, Ruslan Baratov wrote:
>>> export CORRESPONDING_DEVICE_PLATFORM_NAME=iphoneos
>>> export CORRESPONDING_DEVICE_SDK_NAME=iphoneos9.0
>>> export SDK_NAME=iphonesimulator9.0
>> Could you use those variables to avoid hardcoding iphoneos/simulator in
>> the module?
> I see
