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
{{ message }}
This repository was archived by the owner on Feb 4, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 4, 2020. It is now read-only.
I still have this problem with clache being used by gitlab runners.
Each runner has its own copy of a clcache dir, but the build process uses cmake with ninja in a multithreaded way.
Traceback (most recent call last):
File "clcache_main.py", line 2, in <module>
File "clcache\__main__.py", line 1577, in main
File "clcache\__main__.py", line 1604, in processCompileRequest
File "clcache\__main__.py", line 1656, in scheduleJobs
File "concurrent\futures\_base.py", line 398, in result
File "concurrent\futures\_base.py", line 357, in __get_result
File "concurrent\futures\thread.py", line 55, in run
File "clcache\__main__.py", line 1677, in processSingleSource
File "clcache\__main__.py", line 1707, in processDirect
File "clcache\__main__.py", line 1495, in processCacheHit
File "clcache\__main__.py", line 753, in __exit__
File "clcache\__main__.py", line 663, in save
File "contextlib.py", line 89, in __exit__
File "clcache\__main__.py", line 124, in atomicWrite
PermissionError: [WinError 5] Zugriff verweigert: 'C:/Gitlab-Runner/builds/44bc1753/0/smart_optics/Software_Development/someproject/cache\\stats.txt.new' -> 'C:/Gitlab-Runner/builds/44bc1753/0/smart_optics/Software_Development/someproject/cache\\stats.txt'
Activity
izmmisha commentedon Jan 7, 2019
Try to move clcache dir out of user profile dir (
C:\Users\tihomir\clcache->C:\clcachefor example). You can use CLCACHE_DIR environment variable.9a4gl commentedon Jan 7, 2019
Hm, actually I have moved to D:\clcache and I haven't saw this problem anymore. Thanks
apriori commentedon May 8, 2019
I still have this problem with clache being used by gitlab runners.
Each runner has its own copy of a clcache dir, but the build process uses cmake with ninja in a multithreaded way.