[CDash] [EXTERNAL] Re: Reducing upload size

[David Cole]

Sounds like it will almost work.

You'll also likely need a call to
https://cmake.org/cmake/help/latest/command/ctest_read_custom_files.html#command:ctest_read_custom_files
in your ctest script after the configure step.


Let us know if it works out,
David



On Fri, May 19, 2017 at 3:22 PM, Ibanez, Daniel Alejandro
<daibane at sandia.gov> wrote:
> Thanks, David.
>
> We have full control of how to do this, so that’s good.
> I’m not familiar with CTestCustom (as opposed to CTestConfig),
> but here is my best guess at usage:
>
> 1. Create CTestCustom.cmake, put it next to the CTest script.
> 2. In the CTest script, do
>
> configure_file(${CMAKE_CURRENT_LIST_DIR}/CTestCustom.cmake ${CTEST_BINARY_DIRECTORY}/CTestCustom.cmake COPYONLY)
>
> prior to calling ctest_start().
>
> Does that sound right?
> I’ll give it a try.
>
> Dan
>
> On 5/19/17, 1:15 PM, "David Cole" <DLRdave at aol.com> wrote:
>
>     You can set the variable
>     https://cmake.org/cmake/help/latest/variable/CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE.html
>     in a CTestCustom file to limit the amount of output which is recorded
>     in the uploaded XML files for passed tests. (Typically this output is
>     the same from run to run, and does not need to be reported to the
>     dashboard.)
>
>     Since your project uses the stuff from Trilinos, I suspect there's a
>     setting in there somewhere which sets this very high to make it easy
>     for your devs to see the test output generated by "other computers".
>     If you can find a way to set it in your project's CTestCustom file(s)
>     then you should be able to reduce your uploaded volume of data
>     significantly.
>
>     I think the default value for this parameter is something like 1k.
>     (You could check the CMake/CTest source code to verify.)
>
>
>     HTH,
>     David C.
>
>
>
>     On Fri, May 19, 2017 at 1:35 PM, Ibanez, Daniel Alejandro
>     <daibane at sandia.gov> wrote:
>     > Hello,
>     >
>     >
>     >
>     > We operate the following site:
>     >
>     >
>     >
>     > http://my.cdash.org/index.php?project=Albany
>     >
>     >
>     >
>     > It seems that we’re exceeding the upload quota.
>     >
>     > I’m also told that the paid subscription plans are going away or gone.
>     >
>     > So the first question is:
>     >
>     >
>     >
>     > In the long-term is it a good idea for us to plan on hosting our own CDash
>     > instance? Will my.cdash.org be around much longer?
>     >
>     >
>     >
>     > We control the whole process using the scripting feature of CTest and a
>     > fairly elaborate set of scripts, for example see this important file:
>     >
>     >
>     >
>     > https://github.com/gahansen/Albany/blob/42f52bb3ab84deab088ef35448658e9aa12cec76/doc/LCM/build/snl_helpers.cmake
>     >
>     >
>     >
>     > Ideally, we would like to reduce the amount of information uploaded. My
>     > guess is the vast majority of the data is in test output. I know there is a
>     > way to stop CTest from printing test output to the console unless the test
>     > actually fails, is there an equivalent option that affects the uploaded XML
>     > file?
>     >
>     >
>     >
>     > Thanks,
>     >
>     > Dan
>     >
>     >
>     >
>     >
>     > _______________________________________________
>     > CDash mailing list
>     > CDash at public.kitware.com
>     > http://public.kitware.com/mailman/listinfo/cdash
>     >
>
>