Eric Wilhelm wrote:
I was running the tests as my normal user, and it appears that I killed
it as root, or else it didn't properly cleanup at some point. Seems
like it should probably use File::Temp::tempdir(), or at least create
the temp dir inside of the distribution tree.
Can't remove directory /tmp/pp_switch_tests/temp0 (Permission denied) at
a
utomated_pp_test.pl line 6966
Can't remove directory /tmp/pp_switch_tests (Directory not empty) at
autom
ated_pp_test.pl line 6966
--Eric
I suspect that the symptoms exhibited would be the same no matter what
directory is used for temp.
There was a logic behind using known names for temp directories during
the tests. Namely, for ease in knowing the directory names and going
there if there was a problem.
There is a module called ...\contrib\automated_pp_test\prior_to_test.pm
that is invoked prior to every test. I will paste the comments from the
top of prior_to_test.pm below. The basic idea is to make sure each new
test starts afresh, and yet have the results from the current and
previous tests be available just in case there were some kind of
inadvertent interference.
# Outline
# -------
# . chdir to the base directory.
# . Decide which of three possible sub dirs to wipe out,
# which will be tempn where the 'n' is test number mod 3.
# . Wipe out the temp dir and all it's files and sub dirs
# . Recreate the temp dir and four further sub dirs.
# . Assign the temp dir name (the one used by the caller)
# to be passed back up.
#
########################################################################
#
# There are three temp directories used so that we can inspect prior
# test results if there is a crash, as well as the current test
# results. The rationale is that it may be helpful to know what
# we were doing prior to the present test. There should never be
# a relationship, but, ...
