Menu
▾
▴
Re: [Vxl-maintainers] More output on the dashboard
|
From: Wheeler, F. W (G. Research) <wh...@cr...> - 2007-11-14 10:54:47
|
It looks like there is now more test output for the continuous submissions, but not the nightly ones. I suspect the reason is that when cmake copies CTestCustom.cmake from the source tree to the build tree that is too late to effect the current build. But it does have an effect on subsequent builds. So for the 2nd, 3rd, etc. continuous build this works. That's just my hunch. However, this conflicts with my experience with our internal "GEVXL" dashboard. For that project we copy CTestCustom.cmake (actually CTestCustom.ctest) from the source tree to the build tree in the same way, and it effects even the nightly builds. Manual for CTestCustom: http://www.cmake.org/Wiki/CMake_Testing_With_CTest#Customizing_CTest I'm not sure what else to try to get this working on the nighly submissions. Fred -----Original Message----- From: Wheeler, Frederick W (GE, Research)=20 Sent: Tuesday, November 13, 2007 3:33 PM To: vxl...@li... Cc: 'Amitha Perera' Subject: RE: [Vxl-maintainers] More output on the dashboard I just added vxl/config/cmake/Modules/CTestCustom.cmake and set up vxl/CMakeLists.txt to copy it to the build directory, which is where it needs to be for ctest to use it. I think this will do what Amitha is asking for. Here are the contents ... # VXL custom settings for ctest # This file is only used by ctest if it is in the build tree so it is # copied to the build tree by vxl/CMakeLists.txt # default is to report 50 errors and 50 warnings SET (CTEST_CUSTOM_MAXIMUM_NUMBER_OF_ERRORS 500) SET (CTEST_CUSTOM_MAXIMUM_NUMBER_OF_WARNINGS 500) SET (CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE 102400) # default is 1024 SET (CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE 102400) Fred -----Original Message----- From: vxl...@li... [mailto:vxl...@li...] On Behalf Of Amitha Perera Sent: Tuesday, November 13, 2007 2:49 PM To: vxl...@li... Subject: [Vxl-maintainers] More output on the dashboard Folks, Many of the dashboard submissions are truncating the output of the tests at 1024 characters, probably because they are using CTest as a Dart client. E.g. http://www.cs.rpi.edu/research/groups/vxl/Testing/Sites/grc.ge.com/FreeB SD-6.2_gcc-3.2.3_-Wall_-O2_shared/20071113-0300-Nightly/Results/__contri b_brl_bseg_brip_tests_brip_test_histogram.html http://www.cs.rpi.edu/research/groups/vxl/Testing/Sites/lems.brown.edu/L inux-2.6_gcc-4.1.2_-Wall/20071113-0300-Nightly/Results/__contrib_brl_bba s_bsta_tests_bsta_k_medoid.html http://www.cs.rpi.edu/research/groups/vxl/Testing/Sites/IVS-DELL2/Win32- vs8/20071113-1711-Continuous/Results/__contrib_brl_bbas_bnl_tests_bnl_te st_crs_index.html Could the maintainers of the dashboards please large this limit?=20 Without an increase, the test output is essentially useless for debugging. I'm not that familiar with CTest. Perhaps there is a way to commit a file into the vxl source that will cause all CTest clients to have larger buffers? Amitha. ------------------------------------------------------------------------ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Vxl-maintainers mailing list Vxl...@li... https://lists.sourceforge.net/lists/listinfo/vxl-maintainers |