[Insight-developers] ITK Modular: CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE ignored

Bill Lorensen bill.lorensen at gmail.com
Wed Mar 16 12:59:24 EDT 2011


For example I sometimes look at the output of itkSystemInformationTest.

There are other times I look at output of other tests to find problems
on platform I don't have access to.

No matter, this is a regression from what was happening.


On Wed, Mar 16, 2011 at 12:48 PM, David Cole <david.cole at kitware.com> wrote:
> Is 10k too small?
> 100k?
>
> The idea behind truncating the passing test results is that nobody
> cares (and never looks at) what the exact output was for a passed
> test. If you want the output of a passing test, you can just run it
> locally to see the full output.
>
> If you need the full output from an individual test temporarily to see
> its results on another platform you can print "CTEST_FULL_OUTPUT" in
> the stdout output of a test. (Then, after you've seen the output you
> need on the other platform, you can revert that change, and not save
> all that near useless output in CDash again...)
>
> I'm ok with whatever the consensus is here, but I thought I'd mention
> the reasoning behind the default logic to see what people think.
>
> I'd be happier with something closer to the 1k - 10k range, but will
> be happy to set it to whatever most people think is necessary for
> ITK's dashboard results.
>
>
> Let me know, thanks,
> David
>
>
>
> On Wed, Mar 16, 2011 at 12:36 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
>> 1 meg may be too big, but 1k is certainly too small.
>>
>> On Wed, Mar 16, 2011 at 12:26 PM, David Cole <david.cole at kitware.com> wrote:
>>> The file that is actually used for the CTestCustom is:
>>>
>>>  CMake/CTestCustom.cmake.in
>>>  # (line 124 of CMakeLists.txt)
>>>
>>> Which does not have a maximum passed test output size. Not sure why it
>>> changed to *not* include the other one -- looks like the .ctest
>>> version used to be included by the .cmake version. We should just
>>> clean this up to use only one custom file.
>>>
>>> But: do we really want up to 1 Megabyte of each passing test's output
>>> to be stored in CDash?
>>>
>>> (I'm just offering my diagnosis here... I don't have time to work on
>>> any change for this immediately. I can put it on my list for later,
>>> though, if nobody else beats me to it.)
>>>
>>>
>>> David
>>>
>>>
>>> On Wed, Mar 16, 2011 at 10:20 AM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
>>>> The CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE is set to 1000000,
>>>> yet passing tests are reporting:
>>>> http://www.cdash.org/CDash/testDetails.php?test=87831317&build=906357
>>>>
>>>> The file ITK/CMake/CtestCustom.ctest.in has the value:
>>>> SET(CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE 1000000
>>>>
>>>> Bill
>>>> _______________________________________________
>>>> Powered by www.kitware.com
>>>>
>>>> Visit other Kitware open-source projects at
>>>> http://www.kitware.com/opensource/opensource.html
>>>>
>>>> Kitware offers ITK Training Courses, for more information visit:
>>>> http://kitware.com/products/protraining.html
>>>>
>>>> Please keep messages on-topic and check the ITK FAQ at:
>>>> http://www.itk.org/Wiki/ITK_FAQ
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://www.itk.org/mailman/listinfo/insight-developers
>>>>
>>>
>>
>


More information about the Insight-developers mailing list