Page MenuHomePhabricator

mitkPackageTest fails on ubuntu 11.10 dartclient
Closed, ResolvedPublic

Description

Event Timeline

uhhm running the command line as it is run by the test as my local user "mmueller"

/usr/bin/cmake "--build" "/local/muellerm/tray/dartclients/mbi/MITK-MBI-Superbuild-Release-nightly/MITK-superbuild/MITK-build" "--config" "Release" "--target" "package

succeeds with

"CPack: - package: /local/muellerm/tray/dartclients/mbi/MITK-MBI-Superbuild-Release-nightly/MITK-superbuild/MITK-build/MITK-2012.02.99_ra4fb98-Linux.tar.gz generated."

this must be a right/user problem by letting cron run the job

seems to be a time out problem

I am not so sure that this is a timeout problem. Here, the "build" test is failing, which should only take a couple of minutes at most. The timeout problems are related to the "package" tests which usually take like 20-40 minutes.

Sorry, it *is* a "package" test, but for MITK. What is strange is that the test fails after one minute, but the timeout is something like 60 minutes.

will work on it next bugsquashing

[703f9c]: Merge branch 'bug-11129-packagetest-failing'

Merged commits:

2012-03-21 15:47:16 Michael Mueller [8ff811]
forcing PackageTest to be run in serial

works on my dartclient, still failing on two other machines but with different errors:

http://mbits/cdash/testSummary.php?project=2&name=mitkPackageTest&date=2012-03-28

sascha, please have look at mbi074. the package test fails because doxygen is not found (simple):
http://mbits/cdash/testSummary.php?project=2&name=mitkPackageTest&date=2012-06-13

andi same accounts for you: package test is failing on
mbimac05.inet.dkfz-heidelberg.de

please have a look when there is time
http://mbits/cdash/testSummary.php?project=2&name=mitkPackageTest&date=2012-06-13

I think there is a separate bug report for our internal cdash clients. This bug is for the "MITK" product.

On cdash.mitk.org, Linx clients pass all tests. I don't know if we still have Ubuntu 11.10 clients, which this bug seems to address originally.

On it is not a missing doxygen. I found some information that this problem is related to some leavings of an old Xcode installation. I will have a look at it next BS.