|
From: | Jan-Patrick Osterloh |
Subject: | Re: [certi-dev] Setting-up Dashboard submission for CERTI |
Date: | Mon, 26 Sep 2011 19:24:24 +0200 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.22) Gecko/20110902 Lightning/1.0b2 Thunderbird/3.1.14 |
Hi, -------- Original Message -------- Thanks, this works!You proxy must be picky about http protocol version. see: http://www.cmake.org/Bug/print_bug_page.php?bug_id=8903 You should use CMake/CTest version greater than 2.8.1 and use: ctest --http1.0 -S certi-ctest.cmake,Experimental Yes, it is a fresh checkout, and I didn't patch anything (it is not even run on my computer).C:/home/nightlybuild/CERTI-Test/build/Testing/20110921-1618/Build.xml Error message was: The requested URL returned error: 417 Problems when submitting via HTTP Unable to find executable: MessageBufferTests Unable to find executable: MsgBufferTests Unable to find executable: TestHLAtypes Unable to find executable: TestClocks Unable to find executable: TestFedTimeThose Error are the consequence of a failing Build. Since the build failed no executable were produced.The executables are build, and are in "C:\home\nightlybuild\CERTI-Test\build" (and have the .exe ending). I don't know where the problem is. I attach the four xml files, maybe it helps...The Build.xml attached to the mail indicate that the Build failed which is logical because the ctest does a clean checkout & configure & build & test. So the version tested is the CVS HEAD and not your [may be patched] local tree. But fact is, that the test executables and libraries are there, see Photo... And I can manually run the tests (and it seems that they work). If I look in the Test.xml, then I see this: <TestList> <Test>./libHLA/LibHLA_MB_Tests</Test> <Test>./libHLA/LibHLA_MB_Tests_InC</Test> <Test>./libHLA/LibHLAtypes</Test> <Test>./libHLA/LibHLAClocks</Test> <Test>./libRTI/TestLibFedTime</Test> </TestList> Shouldn't this list the MsgBufferTests.exe, etc? These are (in my configuration) listed in ../CERTI-Test/build/ Bye JPO P.S. I uploaded a patch for mingw build, which removes a lot of these warnings on visibility. I started with this, because it is easy to fix and I can get familiar with this patch stuff... Can you give me an advice, which patch I should integrate and test next? -- Dipl. Inform. Jan-Patrick Osterloh FuE Bereich Verkehr | R&D Division Transportation Human Centered Design Group OFFIS FuE Bereich Verkehr | R&D Division Transport Escherweg 2 - 26121 Oldenburg - Germany Phone/Fax: +49 441 97 22-524/502 E-Mail: address@hidden URL: http://www.offis.de |
signature.asc
Description: OpenPGP digital signature
[Prev in Thread] | Current Thread | [Next in Thread] |