[Error 183] Cannot create a file when that file already exists

[cyberwjf]

I'm using Windows 7 + VS2012 Express + Python 2.7. Some of my project got below error, some get passed.

I'm following the setup process for Visual Studio, not sure what kind of problem will cause this issue.

1> Traceback (most recent call last):
1> File "clcache.py", line 1376, in
1> File "clcache.py", line 1250, in main
1> File "clcache.py", line 1281, in processCompileRequest
1> File "clcache.py", line 1343, in processDirect
1> File "clcache.py", line 1340, in
1> File "clcache.py", line 1181, in postprocessNoManifestMiss
1> File "clcache.py", line 1092, in addObjectToCache
1> File "clcache.py", line 284, in setEntry
1> File "clcache.py", line 617, in copyOrLink
1> WindowsError: [Error 183] Cannot create a file when that file already exists
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(347,5): error MSB6006: "CL.exe" exited with code 255.

[frerich]

Three questions to trace this down:

1. Which clcache version are you using? Please make sure that you're using the latest version ,which has some fixes related to concurrent access to the object cache.
2. Do you use parallel compilation (e.g. by invoking cl with more than one source file, or by running multiple invocations of cl in parallel) using the same cache directory?
3. Is your cache directory on a local disk or is it a shared network drive used by multiple hosts?

[cyberwjf]

1. I'm using the latest version of clcache.
2. seems I'm using parallel compilation.
3. It's on my local disk.

Let me try to avoid parallel compilation.

BRs,
Carl Wang

On Fri, Jul 8, 2016 at 8:39 PM, Frerich Raabe notifications@github.com
wrote:

Three questions to trace this down:

Which clcache version are you using? Please make sure that you're
using the latest version ,which has some fixes related to concurrent access
to the object cache.
2.

Do you use parallel compilation (e.g. by invoking cl with more than
one source file, or by running multiple invocations of cl in parallel)
using the same cache directory?
3.

Is your cache directory on a local disk or is it a shared network
drive used by multiple hosts?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#155 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AA4FeSRvodvOk2LP9NpKmDkyZfBzR9rqks5qTkT5gaJpZM4JH5QV
.

[frerich]

Can you reproduce this issue? If so, can you please set the environment variable CLCACHE_LOG=1, then reproduce the error and then send the printed log files? That might shed some light.

[Liyra]

Same error here, following the info with the log variable:
Traceback (most recent call last): (TaskId:22)
File "clcache.py", line 1443, in (TaskId:22)
File "clcache.py", line 1328, in main (TaskId:22)
File "clcache.py", line 1357, in processCompileRequest (TaskId:22)
File "clcache.py", line 1422, in processDirect (TaskId:22)
File "clcache.py", line 1419, in (TaskId:22)
File "clcache.py", line 1261, in postprocessNoManifestMiss (TaskId:22)
File "clcache.py", line 1178, in addObjectToCache (TaskId:22)
File "clcache.py", line 317, in setEntry (TaskId:22)
File "clcache.py", line 647, in copyOrLink (TaskId:22)
FileExistsError: [WinError 183] Cannot create a file when that file already exists: 'D:\clcache\objects\2f\2f583e9f9181cc2578f56d07f6bf42d6\object.tmp' -> 'D:\clcache\objects\2f\2f583e9f9181cc2578f56d07f6bf42d6\object' (TaskId:22)
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\clcache.py Parsing given commandline '[ #CommandLine# ]' (TaskId:22)
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\clcache.py Expanded commandline '[ #CommandLine# ]' (TaskId:22)
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\clcache.py Compiler source files: #SourcePath#
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\clcache.py Compiler object file: #ObjFile# (TaskId:22)
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\clcache.py Invoking real compiler as 'C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\cl_original.exe'
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\clcache.py Real compiler returned code 0 (TaskId:22)
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\clcache.py Adding file #ObjFile# to cache using key 2f583e9f9181cc2578f56d07f6bf42d6 (TaskId:22)
Failed to execute script clcache (TaskId:22)
(TaskId:22)
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\clcache.py Child: ' #CommandLine# '
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\clcache.py Child: ' #CommandLine# '
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\clcache.py Child: ' #CommandLine# '
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\clcache.py Child: ' #CommandLine# '
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(341,5): error MSB6006: "CL.exe" exited with code -1.

[Jimilian]

@Liyra , can you describe your environment? Pure clcache + cl.exe? Incredibuild+clcache + cl.exe? Local run or Continuous integration? If CI, how much executions do you have in same time?

[Liyra]

I use only clcache 3.2 with visual studio community 2013 (I don't use Incredibuild), on my local machine, just clicking on the build solution button in visual, so I assume it's compiling in parallel. The solution I am working on is composed of more or less 100 projects, and this error message occurs only for 4-5.
Hope it helps !

[Jimilian]

@Liyra, @webmaster128 suggested workaround that works for me - use CLCACHE_NODIRECT=1.

[webmaster128]

@Liyra, @webmaster128 suggested workaround that works for me - use CLCACHE_NODIRECT=1.

The workaround is for missing include files, not for this issue here (existing cache "object" files). If disabling direct mode helps anyway, then direct mode is responsible for this issue.

[Liyra]

I have the same errors with the CLCACHE_NODIRECT variable set to 1, but the errors occurs for almost every project instead of 4-5.

[webmaster128]

@Liyra Is it possible, that your build environment builds the same file twice at the same time?

[Liyra]

I really don't know, I just use the default parameters in visual studio, I will assume that everything is correctly handled and only compiled once.

[webmaster128]

Ahhhhahahaha muhaa – boom, there is a logic error:

When a manifest is newly created it is not checked if the object is already in cache or not. Instead it is assumed the cache object does not exists. This happens because only nodirect was used before and then you switch to direct mode or manifests have been cleaned.

Temporary workaround would be:

1. Clear cache entirely
2. Use CLCACHE_NODIRECT

I think I'll provide a patch as soon as frerich is back and the PRs list is reduced a bit.