shutil.rmtree should be avoided in almost all cases safe_rmtree has its usage in tasks module, but innards are replaced with koji.util.rmtree, so we don't have two implementations of same task
Related: https://pagure.io/koji/issue/648
need to adjust unit test for recycle_build safe_rmtree must return 0 on success (checked in updateBuildroots) stale comment still refers to find command might was well fix that bare except
changes here: https://github.com/mikem23/koji-playground/commits/pagure/pr/658
ah, and I need to update the unit test again for that
Hmm, doesn't look like you are setting up the /mnt/folder that these new tests refer to.
/mnt/folder
The TasksTestCase class is kind of cluttered and I'm not sure these new tests benefit from being in there. Maybe it would be better to have a separate class with its own setUp/tearDown?
TasksTestCase
rebased onto 5acf3f9f8fdd3346a34c87eb4635bb94ad893422
Directory path is not touched, as all system calls are mocked. I think it is not necessary to set up real files, as all os.* calls are mocked.
Created separate class for safe_rmtree tests.
ah , of course
For completeness, we should also change the embedded rmtree code in delete/reset_build. Change added here:
https://github.com/mikem23/koji-playground/commits/pagure/pr/658
1 new commit added
Updated with your commit.
rebased onto 09182866a5194181c127fd359ff8ba4301907f02
Commit 423eac9e fixes this pull-request
Pull-Request has been merged by mikem@redhat.com
shutil.rmtree should be avoided in almost all cases
safe_rmtree has its usage in tasks module, but innards are replaced with
koji.util.rmtree, so we don't have two implementations of same task
Related: https://pagure.io/koji/issue/648