Interesting, Adam.

Does the directory

/vols/mice3/adobbs/maus/tracker_devel/files/PID/test_200MeV_pi_plus_2014_03_19T14_29_05_882157

If it does, are you able to remove it by hand with rm -rf ?

More interesting the more I look at it. The directories do exist, but are empty after the test terminates. I have tried removing them from the command line and then re-running the test, but the same error crops up. As far as I can tell the right command to remove a directory tree in python is being used by the test (shutil.rmtree) and when I tried to remove one of those directories by hand in python, it did it without problem.

Note: I see the same thing running on both the Imperial HEP machines running CentOS, and the RAL PPD cluster, both using a clean version of MAUS-v0.8.3 (I think I tried it on my Ubuntu laptop too...)

What are the file permissions for the directory(ies) that are left hanging around?

I have pushed a fix to lp:~durga/maus/1435
asking it to forcibly remove the directory with rm -rf

        #shutil.rmtree(PDFdirectory)
        os.system('rm -rf %s' % PDFdirectory)

I can't reproduce the error here, so can you try it and let me know if the fix resolves the problem?

I just ran the tests and received this exact same set of errors, building from the tracker development branch on one of the Imperial machines.