Allergic to failing builds, I always look at ways to stabilize our build process. Of course this is if the tooling doesn’t start to work against us. Last month we had some failing builds because the code coverage process was not closed thereby keeping the coverage files locked. This resulted in following error:
The process cannot access the file ‘data.coverage' because it is being used by another process.
Killing the VSPerfMon.exe process on the build server solves the problem but I don’t think we can see this as ‘the solution’. I haven’t find an alternative yet, so all ideas are welcome.
And of course this only happens in some occasions. Some people complained about the same issue on the MSDN forum.