Occurs on mbi029/mbi025, archlinux.
They do work when started manually though,
but take a VERY long time:
7/340 Test #7: mitkProjectTemplatePackageTest ........................................... Passed 268.28 sec
Start 8: mitkPackageTest
8/340 Test #8: mitkPackageTest .......................................................... Passed 561.03 secmight be some timeout-issue ?
it seems to be limited to Arch Systems.
seems to be python related:
Run CPack packaging tool...
CPack: Create package using TGZ
CPack: Install projects
CPack: - Run preinstall target for: AwesomeProject
CPack: - Install project: AwesomeProject
CMake Error at /home/christoph/data/dartclients/gcc-mitk-debug/MITK-sb-D-n/MITK-build/PT-bin/AwesomeProject-build/Apps/AwesomeApp/cmake_install.cmake:6347 (file):
file INSTALL cannot find "/home/christoph/data/dartclients/gcc-mitk-debug/MITK-sb-D-n/Python-install/include/python3.4/pyconfig.h".
Call Stack (most recent call first):
/home/christoph/data/dartclients/gcc-mitk-debug/MITK-sb-D-n/MITK-build/PT-bin/AwesomeProject-build/Apps/cmake_install.cmake:37 (include) /home/christoph/data/dartclients/gcc-mitk-debug/MITK-sb-D-n/MITK-build/PT-bin/AwesomeProject-build/cmake_install.cmake:61 (include)
It's a python bug. MITK builds python 2.7 in the superbuild.
Your build want's to include the python config from your installed python 3.4 version which seems to be a bug in build/install scripts.
Wrong Path:
/home/christoph/data/dartclients/gcc-mitk-debug/MITK-sb-D-n/Python-install/include/python3.4/pyconfig.h
This are two unrelated problems:
First the cdash reports an error due to a time out, possible soultion:
increase the timeout for packaging tests ?? as pasted the package test simply takes to long.
The second is caused by the Project Generator, that cannot link the proper Python libs.