Re: [certi-dev] Setting-up Dashboard submission for CERTI

[Eric Noulard]

2011/9/26 Jan-Patrick Osterloh <address@hidden>
>
> Hi,
>
>
> -------- Original Message  --------
>
> 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
>
> Thanks, this works!
>
> 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: TestFedTime
>
> Those 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.
>
> Yes, it is a fresh checkout, and I didn't patch anything (it is not even run 
> on my computer).
>
> But fact is, that the test executables and libraries are there, see Photo...

Yes but the build failed:
http://my.cdash.org/buildSummary.php?buildid=238570

Thus the tests were not run:
http://my.cdash.org/viewTest.php?onlynotrun&buildid=238570

> 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/

./libHLA/LibHLA_MB_Tests is the name of the test
MsgBufferTests.exe, is the executable run for the previous test.


test name may be different from the command, see in libHLA/CMakeLists.txt

ADD_TEST(LibHLA_MB_Tests MessageBufferTests)

> 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...

Just merged it to CVS HEAD, patch was ok.
One small remark, try to use space indentation and not tab indentation
this gives more consistent results over variour editors.
You should be able to configure your favorite editor to insert space
instead of tab.

Thanks.

> Can you give me an advice, which patch I should integrate and test next?

The heart of the problem on Windows is the circular dep problem,
fixing this should be the next step for a clean Windows build.

re-read this thread and refs therein:
http://lists.nongnu.org/archive/html/certi-devel/2011-09/msg00002.html
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org