-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Labels
Milestone
Comments
dotnet-issue-labeler
bot
added
the
untriaged
New issue has not been triaged by the area owner
label
Nov 24, 2021
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
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
This is part of the build race. I’ll get this fixed after we update to the RTM SDK. |
Thanks @jkoritzinsky . I found a very similar failure in another PR. This time, it's not the Affected legs:
Error message:
|
This was referenced Nov 30, 2021
ghost
added
the
in-pr
There is an active PR which will close this issue when it is merged
label
Nov 30, 2021
ghost
removed
the
in-pr
There is an active PR which will close this issue when it is merged
label
Nov 30, 2021
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
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
The text was updated successfully, but these errors were encountered: