Closed WhitWaldo closed 1 year ago
Hello @WhitWaldo, thank you for submitting this issue. We will try to get back to you as soon as possible. Note to the PostSharp team, this ticket is being tracked in our dashboard under ID TP-33464.
Following up, this is a regression as the build works without issue when I roll back to v2023.1.9.
Hello @WhitWaldo , may I ask you to collect logs of this behavior as described at https://doc.metalama.net/conceptual/configuration/creating-logs and send us the logs?
In the logs, you should also see which file is causing this. Please try to delete the file to unblock the failing build.
Hello @prochan2 - are those instructions valid for a build server as well where there is no active and running IDE instance?
I think no log will be needed.
It's probably not a regression but a random race so cleaning the temp directory and retrying should be ok.
This should be fixed in Metalama 2023.2.2-rc.
Experienced this again on the build server after migrating to 2023.3.4-preview while building a solution with nothing but a TransitiveProjectFabric in it. Deleting the file works right up until the next time it builds.
Resolved it by adding a clean step to the workspace job so it always starts the build with a clean directory, but it means the underlying issue hasn't been resolved. Again, no idea why this is only an issue on the build server and never locally.
I got the same issue internally so I'm reopening the ticket.
This, hopefully, has been solved in 2023.3 rc.
I received an error on my build server today (running Windows Server 2019 Datacenter edition in Azure) on the latest preview build as follows:
[error]CSC(0,0): Error LAMA0001: Unexpected exception occurred in Metalama: Cannot create a file when that file already exists. Exception details are in 'C:\windows\ServiceProfiles\NetworkService\AppData\Local\Temp\Metalama\CrashReports\2023.2.1-preview\exception-98783161-ec5a-4f86-838b-f282f5973da5.txt'.
And here's the crash report itself:
The same project builds fine on my local dev box (Windows 10, x64) without issue.