Taskflow/iRODS tests leave behind orphaned project collections in vault

[mikkonie]

Something I managed to do while setting up SODAR dev env on my new dev machine:

• Set up a fresh irods-test container with no existing data
• Run the full suite of SODAR Django tests which execute without problems
• Afterwards, a large number of empty project directories and their subdirectories remain in the irods-test vault
  • No files, just empty dirs
• The ICAT server on irods-test shows there is no projects collection under sodarZone

It seems something fails or is not correctly done in test tearDown() methods and/or clear_irods_test_data(). I have no idea how long this problem has persisted.

Of course, this is no problem in CI as the server is wiped after each run. But on a dev environment we can quickly accumulate a quite a a lot of redundant empty directories. This should be fixed.

Next step: try to identify which tests cause this and why.

[mikkonie]

It seems this happens with tests initiating data objects. That makes sense, as the vault should only be affected if we manipulate data objects.

I'm guessing I do something wrong in cleanup when removing files?

Example of a test which can be used to reproduce this:

irodsadmin.tests.test_commands.TestCheckSampleAccess.test_command_extra_user_obj