Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI failure (net48 x86): GenerateResource.cache is being used by another process #62028

Closed
carlossanlop opened this issue Nov 24, 2021 · 4 comments · Fixed by #62156
Closed

CI failure (net48 x86): GenerateResource.cache is being used by another process #62028

carlossanlop opened this issue Nov 24, 2021 · 4 comments · Fixed by #62156
Labels
area-Interop-coreclr source-generator Indicates an issue with a source generator feature
Milestone

Comments

@carlossanlop
Copy link
Member

carlossanlop commented Nov 24, 2021

.dotnet\sdk\6.0.100-rc.2.21505.57\Microsoft.Common.CurrentVersion.targets(3264,5):
error MSB3101: (NETCORE_ENGINEERING_TELEMETRY=Build)
Could not write state file
"D:\a\_work\1\s\artifacts\obj\Microsoft.Interop.SourceGeneration\netstandard2.0-Release\Microsoft.Interop.SourceGeneration.csproj.GenerateResource.cache".
The process cannot access the file
'D:\a\_work\1\s\artifacts\obj\Microsoft.Interop.SourceGeneration\netstandard2.0-Release\Microsoft.Interop.SourceGeneration.csproj.GenerateResource.cache'
because it is being used by another process.

The failure happened in the CI of this PR: #59850

It was the net48 x86 leg:
https://github.com/dotnet/runtime/pull/59850/checks?check_run_id=4316507944

Here's the log:
https://dev.azure.com/dnceng/public/_build/results?buildId=1485041&view=logs&j=79ebbb2e-07f2-5457-c5e5-132dd7ee4ba8&t=19d75d51-494c-5498-c708-7a0aae08aa93

@elinor-fung @jkoritzinsky


Variant: "File already exists" instead of "File used by another process":
https://dev.azure.com/dnceng/public/_build/results?buildId=1490663&view=logs&j=924a68e5-ba21-56d0-bfb9-0b068c6fae9a&t=8c8cf4a0-c3ab-58ea-a108-e7df9b47cd9f&l=2889

.dotnet/sdk/6.0.100/Microsoft.Common.CurrentVersion.targets(2304,5): error MSB3101:
(NETCORE_ENGINEERING_TELEMETRY=Build) Could not write state file
"/Users/runner/work/1/s/artifacts/obj/Microsoft.Interop.SourceGeneration/netstandard2.0-Debug/Microsoft.Interop.SourceGeneration.csproj.AssemblyReference.cache".
The file
'/Users/runner/work/1/s/artifacts/obj/Microsoft.Interop.SourceGeneration/netstandard2.0-Debug/Microsoft.Interop.SourceGeneration.csproj.AssemblyReference.cache'
already exists.
@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Nov 24, 2021
@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@AaronRobinsonMSFT
Copy link
Member

/cc @jkoritzinsky @elinor-fung

@AaronRobinsonMSFT AaronRobinsonMSFT added source-generator Indicates an issue with a source generator feature and removed untriaged New issue has not been triaged by the area owner labels Nov 27, 2021
@AaronRobinsonMSFT AaronRobinsonMSFT added this to the 7.0.0 milestone Nov 27, 2021
@jkoritzinsky
Copy link
Member

This is part of the build race. I’ll get this fixed after we update to the RTM SDK.

@carlossanlop
Copy link
Member Author

carlossanlop commented Nov 30, 2021

Thanks @jkoritzinsky .

I found a very similar failure in another PR. This time, it's not the *.cache file that is being used, but DllImportGenerator.dll:

#62134

Affected legs:

  • Libraries Build windows allConfigurations x64 Debug (log)
  • Libraries Build windows net48 x86 Release (log)

Error message:

CSC(0,0): error CS2012: (NETCORE_ENGINEERING_TELEMETRY=Build)
Cannot open 'D:\a\_work\1\s\artifacts\obj\DllImportGenerator\netstandard2.0-Debug\Microsoft.Interop.DllImportGenerator.dll' for writing --
'The process cannot access the file 'D:\a\_work\1\s\artifacts\obj\DllImportGenerator\netstandard2.0-Debug\Microsoft.Interop.DllImportGenerator.dll'
because it is being used by another process.'

@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Nov 30, 2021
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Nov 30, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Dec 31, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Interop-coreclr source-generator Indicates an issue with a source generator feature
Projects
None yet
4 participants