[vtk-developers] Possible legacy directory in python testing.

[Bill Lorensen]

According to Wrapping.Python/vtk/test/Testing.py
the path to the testing directory is determined by:

    -T /path/to/valid/temporary_dir/
    --temp-dir /path/to/valid/temporary_dir/

          This is a path to the directory where the image differences
          are written.  If this option is not set via the command line
          the environment variable VTK_TEMP_DIR is used.  If the
          environment variable is not set the value defaults to
          '../../../Testing/Temporary'.

For VTK6, the default should be
../../../../Testing/Temporary

I just pushed a patch to gerrit to resolve the problem.

However, in the future I think we should explicitly specify -T in the
add_test commands for python tests. We do that for tcl and cxx tests.
It's a bit too tricky to rely on defaults in my opinion.

Bill


On Thu, May 24, 2012 at 3:47 AM, Andrew Maclean
<andrew.amaclean at gmail.com> wrote:
> Hi Marcus,
> I have been monitoring TestParametricFunctions and from the dashboard it
> seems that it fails because it is trying to write the test files
> to /Common/Testing/Temporary/ which does not exist. On my linux machine, if
> I create this directory then the test runs. I can confirm this on on my
> machine running Ubuntu 64-bit linux.
> I am seeing the same thing on londinium.kitware for both clang and gcc.
> It is passing on the Macs andhythloth.kitware.
> The test also runs on my windows 64-bit machine and passed.
>
> I am pretty ignorant here as to whether this directory is created on the fly
> and fails because Testing does not exist in Common or whether it is
> something else. It is odd that both Mac and my windows machine run the test
> Ok.
>
>
> Andrew
>
>
>
> --
> ___________________________________________
> Andrew J. P. Maclean
>
> ___________________________________________



-- 
Unpaid intern in BillsBasement at noware dot com