test_import.py cannot run twice

[samwaseda]

test_import.py cannot run twice because somehow pyiron fails to delete jobs in the first run when the tests finish. In the second run these remaining jobs from the first run apparently make a problem.

[samwaseda]

It looks like there are multiple entries created when the jobs are imported with the same job name. On top of this, it looks like the job has itself as a child job, so that when it tries to delete the child job, it cannot identify the job.

[samwaseda]

So I'm not getting any comment here but I'm gonna keep posting my findings to use it as my log book.

• The problem does not occur with the newly updated import and export example. That's a good sign.
• Also, when each test is executed individually, there's no error/problem
• Based on this, I thought moving everything from setUpClass to setUp (same for tearDownClass) could solve the problem, but this created other problems.

[pmrv]

Ah, I remember this issue when running tests locally. It might have been that the project that the test imports into is not the same as the one that gets cleared after the test, but I'm not sure anymore and I never quite fixed it.

[liamhuber]

Ah, I remember this issue when running tests locally. It might have been that the project that the test imports into is not the same as the one that gets cleared after the test, but I'm not sure anymore and I never quite fixed it.

Ditto. I even still have a fix_archive_tests branch on my local repo that I'm pretty sure was trying to address exactly this, but I got frustrated and quit before I got it solved.

[samwaseda]

Yeah it's super frustrating, especially the errors are really not helpful.

I kept digging down, and now I got the feeling that there's a problem with nested projects. It occurs namely even when there are only these two tests: test_unpack_to_nested_project and test_unpack_from_other_dir_uncompress, but somehow if each of them is run individually the problem does not occur.

[samwaseda]

It looks like the opposite is also the case: if I run all tests except for these two, they pass as well.

[samwaseda]

Interestingly, there’s also no problem if only one of them is disabled. So probably something in tearDownClass prevents the problem.