Tilo Wiedera
Tilo Wiedera
> I've re-enabled clcache in our CI now and will report if any errors arise with CLCACHE_OBJECT_CACHE_TIMEOUT_MS=120000. I've just taken a look at our CI builds and seen that our...
> For what it's worth, synchronising concurrent accesses to the cache is implemented by dividing the cache into 256 'sections' and then maintaining a lock for each section. Okay, so...
> you don't happen to have the cache directory on a network drive or some aggressive virus scanner which tracks file accesses, do you? :-) Good remark. Our virus scanner...
> what virus scanner is that (and what setting did you use)? Even though this is probably me being overly precautious I would prefer not to talk about our security...
Can't give any new info yet. I'll have to do some more testing and will report back.
I've run some tests but didn't come up with any issues. I've even switched to the old state (fe99fa6), used excessive on-access virus scanning, and lowered the timeout to 500ms...
Happened again, might be related to un-setting `CLCACHE_SERVER`.
@frerich good job! > uploading the generated output somewhere would be great Will do!
This option is particularly interesting since it would allow us to use `/Debug:FASTLINK`.