You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From time to time there's a conflict when PDepends tries to flush the cache and there's another execution in parallel. The output I receive in a Jenkins job is something similar to:
One possible solution would be to isolate the cache of PDepend not just per user as it is now, but for process. Do this is so easy, you just need to change in PDepend\DependencyInjection\Configuration(88):
But this has an undesired side effect, the implemented cache flush will not work correctly because each cache is saved in a separated directory that will probably never cleaned up by any later PDepend execution. It should be changed to check not just this cache directory that includes the PID, but the generic cache directory.
The text was updated successfully, but these errors were encountered:
Very sad, but this is an issue that came up several times before :( Using the pid is not a good idea because then pdepend would floud your file system.
Since the cache cleanup is not a critical thing, I will now try to fix this issue by letting unlink and rmdir silently fail.
From time to time there's a conflict when PDepends tries to flush the cache and there's another execution in parallel. The output I receive in a Jenkins job is something similar to:
One possible solution would be to isolate the cache of PDepend not just per user as it is now, but for process. Do this is so easy, you just need to change in PDepend\DependencyInjection\Configuration(88):
By something like:
But this has an undesired side effect, the implemented cache flush will not work correctly because each cache is saved in a separated directory that will probably never cleaned up by any later PDepend execution. It should be changed to check not just this cache directory that includes the PID, but the generic cache directory.
The text was updated successfully, but these errors were encountered: